From: BillStuff <billstuff2001@sbcglobal.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Raid5 hang in 3.14.19
Date: Tue, 14 Oct 2014 11:55:00 -0500 [thread overview]
Message-ID: <543D5564.9000101@sbcglobal.net> (raw)
In-Reply-To: <20141014124245.69b143e2@notabene.brown>
[snip]
On 10/13/2014 08:42 PM, NeilBrown wrote:
> Write errors start happening.
>
> You should only get a write error if no writes successfully completed to
> in_sync, non-faulty devices.
> It is possible that the write to sdg3 completed before it was marked in-sync,
> and the write to sdh3 completed after it was marked as faulty.
> How long after recovery completes do you fail the next device?
> The logs suggest it is the next second, which could be anywhere from 1msec
> to 1998 msecs.
>
>
> NeilBrown
>
FYI Neil: Running through my logs, I noticed 6 of these failures in my
testing
over the past few days. All "recovery completed, wait a second, fail the
other
drive" cases. Same signature in the logs. Apparently things kept working
until
the filesystem tripped on its journal and fell over.
So the upshot is this seems reasonably reproducible.
-Bill
prev parent reply other threads:[~2014-10-14 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 22:33 Raid5 hang in 3.14.19 BillStuff
2014-09-29 2:25 ` NeilBrown
2014-09-29 3:56 ` BillStuff
2014-09-29 4:08 ` NeilBrown
2014-09-29 4:28 ` BillStuff
2014-09-29 4:43 ` NeilBrown
2014-09-29 21:59 ` NeilBrown
2014-09-30 4:19 ` BillStuff
2014-09-30 21:21 ` BillStuff
2014-09-30 22:54 ` NeilBrown
2014-10-05 16:05 ` BillStuff
2014-10-14 1:42 ` NeilBrown
2014-10-14 14:56 ` BillStuff
2014-10-14 16:55 ` BillStuff [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=543D5564.9000101@sbcglobal.net \
--to=billstuff2001@sbcglobal.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.