From: Philip Espunkt <p0h0i0l0i0p@gmail.com>
To: kreijack@inwind.it
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [BUG] Btrfs scrub sometime recalculate wrong parity in raid5
Date: Fri, 19 Aug 2016 15:17:50 +0200 [thread overview]
Message-ID: <CAEAFGC-4BfrKJskRZDUrJ3f9VY8KK0FtNPuc1P4eSdc4aagDTA@mail.gmail.com> (raw)
> On 07/12/2016 05:50 PM, Goffredo Baroncelli wrote:
>>
>> most of the time, it seems that btrfs-raid5 is not capable to
>> rebuild parity and data. Worse the message returned by scrub is
>> incoherent by the status on the disk. The tests didn't fail every
>> time; this complicate the diagnosis. However my script fails most
>> of the time.
Have you opened a bug ticket at http://bugzilla.kernel.org/?
I think that would be useful for tracking.
Philip
next reply other threads:[~2016-08-19 13:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 13:17 Philip Espunkt [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-12 21:50 [BUG] Btrfs scrub sometime recalculate wrong parity in raid5: take two Goffredo Baroncelli
2016-07-16 15:51 ` [BUG] Btrfs scrub sometime recalculate wrong parity in raid5 Jarkko Lavinen
2016-07-17 19:46 ` Jarkko Lavinen
2016-07-18 18:56 ` Goffredo Baroncelli
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=CAEAFGC-4BfrKJskRZDUrJ3f9VY8KK0FtNPuc1P4eSdc4aagDTA@mail.gmail.com \
--to=p0h0i0l0i0p@gmail.com \
--cc=kreijack@inwind.it \
--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 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.