From: Jarkko Lavinen <jlavi@iki.fi>
To: linux-btrfs@vger.kernel.org
Subject: Re: [BUG] Btrfs scrub sometime recalculate wrong parity in raid5
Date: Sat, 16 Jul 2016 18:51:11 +0300 [thread overview]
Message-ID: <20160716155111.GA9751@ks392938.kimsufi.com> (raw)
In-Reply-To: <da6e9c30-02a0-39fc-3c67-d0af4fd5bf51@inwind.it>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On 07/12/2016 05:50 PM, Goffredo Baroncelli wrote:
> Using "btrfs insp phy" I developed a script to trigger the bug.
Thank you for the script and all for sharing the raid5 and scrubbing issues. I have been using two raid5 arrays and ran scrub occasionally without any problems lately and been in false confidence. I converted successfully raid5 arrays into raid10 without any glitch.
I tried to modify the shell script so that instead of corrupting data with dd, a simulated bad block is created with device mapper. Modern disks are likely to either return the correct data or an error if they cannot.
The modified script behaves very much like the original dd version. With dd version I see wrong data instead of expected data. With simulated bad block I see no data at all instead of expected data since dd quits on read error.
Jarkko Lavinen
[-- Attachment #2: h.sh --]
[-- Type: application/x-sh, Size: 6526 bytes --]
next prev parent reply other threads:[~2016-07-16 16:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:50 [BUG] Btrfs scrub sometime recalculate wrong parity in raid5: take two Goffredo Baroncelli
2016-07-14 21:20 ` Chris Mason
2016-07-15 4:39 ` Andrei Borzenkov
2016-07-15 13:20 ` Chris Mason
2016-07-15 15:10 ` Andrei Borzenkov
2016-07-15 15:21 ` Chris Mason
2016-07-15 16:30 ` Goffredo Baroncelli
2016-07-15 16:28 ` Goffredo Baroncelli
2016-07-15 16:29 ` Chris Mason
2016-07-15 16:34 ` Andrei Borzenkov
2016-07-16 15:51 ` Jarkko Lavinen [this message]
2016-07-17 19:46 ` [BUG] Btrfs scrub sometime recalculate wrong parity in raid5 Jarkko Lavinen
2016-07-18 18:56 ` Goffredo Baroncelli
-- strict thread matches above, loose matches on Subject: below --
2016-08-19 13:17 Philip Espunkt
2016-06-25 12:21 Goffredo Baroncelli
2016-06-25 17:25 ` Chris Murphy
2016-06-25 17:58 ` Chris Murphy
2016-06-25 18:42 ` Goffredo Baroncelli
2016-06-25 22:33 ` Chris Murphy
2016-06-26 9:20 ` Goffredo Baroncelli
2016-06-26 16:43 ` Chris Murphy
2016-06-26 2:53 ` Duncan
2016-06-26 22:33 ` ronnie sahlberg
2016-06-26 22:38 ` Hugo Mills
2016-06-27 3:22 ` Steven Haigh
2016-06-27 3:21 ` Steven Haigh
2016-06-27 19:47 ` Duncan
2016-06-27 3:50 ` Christoph Anton Mitterer
2016-06-27 4:35 ` Andrei Borzenkov
2016-06-27 16:39 ` Christoph Anton Mitterer
2016-09-21 7:28 ` Qu Wenruo
2016-09-21 7:35 ` Tomasz Torcz
2016-09-21 9:15 ` Qu Wenruo
2016-09-21 15:13 ` Chris Murphy
2016-09-22 2:08 ` Qu Wenruo
2016-09-22 2:44 ` Chris Murphy
2016-09-22 3:00 ` Qu Wenruo
2016-09-22 3:12 ` Chris Murphy
2016-09-22 3:07 ` Christoph Anton Mitterer
2016-09-22 3:18 ` Qu Wenruo
2016-09-21 15:02 ` Chris Murphy
2016-11-04 2:10 ` Qu Wenruo
2016-11-05 7:23 ` Goffredo Baroncelli
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=20160716155111.GA9751@ks392938.kimsufi.com \
--to=jlavi@iki.fi \
--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;
as well as URLs for NNTP newsgroup(s).