From: Martin Steigerwald <Martin@lichtvoll.de>
To: "Hugo Mills" <hugo@carfax.org.uk>,
linux-btrfs@vger.kernel.org,
"Ronnie Collinson" <notthinking@gmail.com>,
"Michael Kjörling" <michael@kjorling.se>
Subject: Re: How does btrfs behave on checksum mismatch?
Date: Sun, 28 Oct 2012 14:36:24 +0100 [thread overview]
Message-ID: <201210281436.24540.Martin@lichtvoll.de> (raw)
In-Reply-To: <20121028132639.GC5042@carfax.org.uk>
Am Sonntag, 28. Oktober 2012 schrieb Hugo Mills:
> On Sun, Oct 28, 2012 at 02:23:51PM +0100, Martin Steigerwald wrote:
> > Am Sonntag, 28. Oktober 2012 schrieb Ronnie Collinson:
> > > In a raid1 situation, it will also rewrite the effected data, on
> > > the drive that failed the checksum
> >
> > Will it do so without an explicit scrub?
>
> If a failed checksum is detected, yes.
>
> If there's a bad block, and the FS happens to read the good copy
> first, it won't fix it, because it hasn't tried reading the bad copy
> yet.
Ah, okay. I think I read some while ago in a case of bad checksum detected
it won´t repair automatically. Has this been changed?
Anyway, a regular scrub still makes sense, as BTRFS only reads files that
applications demand and BTRFS may read from a good copy as you pointed
out.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-10-28 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-27 21:56 How does btrfs behave on checksum mismatch? Michael Kjörling
2012-10-27 22:02 ` Hugo Mills
2012-10-27 22:09 ` Michael Kjörling
2012-10-28 12:23 ` Ronnie Collinson
2012-10-28 13:23 ` Martin Steigerwald
2012-10-28 13:26 ` Hugo Mills
2012-10-28 13:36 ` Martin Steigerwald [this message]
2012-10-28 13:39 ` Hugo Mills
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=201210281436.24540.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=michael@kjorling.se \
--cc=notthinking@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.