From: Christoph Groth <cwg@falma.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs csum failed, scrub ok
Date: Tue, 27 Mar 2012 18:59:49 +0200 [thread overview]
Message-ID: <87d37yt1x6.fsf@falma.de> (raw)
In-Reply-To: 4F71EED2.70706@jan-o-sch.net
Jan Schmidt <list.btrfs@jan-o-sch.net> writes:
> On 27.03.2012 18:24, cwillu wrote:
>> On Tue, Mar 27, 2012 at 4:57 AM, Christoph Groth <cwg@falma.de> wrote:
>>> A scrub done the morning after the incident also didn't find any
>>> problems:
>>>
>>> root@mim:/home/cwg# btrfs scrub status /
>>> scrub status for 2da00153-f9ea-4d6c-a6cc-10c913d22686
>>> scrub started at Tue Mar 27 10:37:49 2012 and finished after 3921 seconds
>>> total bytes scrubbed: 550.20GB with 0 errors
>>
>> If btrfs is able to find a good copy, it will fix the bad copy automatically.
>
> It does mention this in your logs, though. Grep for "repair", if it
> doesn't occur, btrfs didn't repair any failures.
"repair" doesn't occur in the logs. Actually, there are no other
entries from btrfs.
So why didn't btrfs try to repair a block it believed to be bad?
prev parent reply other threads:[~2012-03-27 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 10:57 btrfs csum failed, scrub ok Christoph Groth
2012-03-27 11:08 ` Roman Mamedov
2012-03-27 11:55 ` Christoph Groth
2012-03-27 16:24 ` cwillu
2012-03-27 16:46 ` Jan Schmidt
2012-03-27 16:59 ` Christoph Groth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d37yt1x6.fsf@falma.de \
--to=cwg@falma.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox