From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: "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:23:51 +0100 [thread overview]
Message-ID: <201210281423.51427.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAGa+R32R83cAWLQO4Xgwcvp22r1oPkWhmEOMiWB1HUTSb=r18g@mail.gmail.com>
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?
--
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:23 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 [this message]
2012-10-28 13:26 ` Hugo Mills
2012-10-28 13:36 ` Martin Steigerwald
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=201210281423.51427.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).