From: Joel Young <jdy@cryregarder.com>
To: linux-raid@vger.kernel.org
Subject: Re: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
Date: Thu, 14 Mar 2013 22:13:46 +0000 (UTC) [thread overview]
Message-ID: <loom.20130314T215046-573@post.gmane.org> (raw)
In-Reply-To: 3CD9214B-FAE8-4DA5-BDBC-7A5FEB5AEC4B@colorremedies.com
Chris Murphy <lists <at> colorremedies.com> writes:
>
>
> On Mar 13, 2013, at 10:03 PM, Joel Young <jdy <at> cryregarder.com> wrote:
> > mdadm /dev/md0 --fail /dev/loop1
> > mdadm /dev/md0 --fail /dev/loop2
>
> In this case md0 is failed. And thus md2 is failed.
>
Yes md2 is broken, but it isn't failed according to:
[root@quickstep delme_images]# mdadm --detail /dev/md2
/dev/md2:
Version : 1.2
Creation Time : Wed Mar 13 18:25:17 2013
Raid Level : raid0
Array Size : 406528 (397.07 MiB 416.28 MB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Wed Mar 13 18:25:17 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Chunk Size : 512K
Name : quickstep:2 (local to host quickstep)
UUID : ca94a237:d63c25be:ff64fe0f:a41be44c
Events : 0
Number Major Minor RaidDevice State
0 9 1 0 active sync /dev/md0
1 9 3 1 active sync /dev/md1
In /var/log/messages I get a bunch of buffer I/O errors on the device and
a warning in drivers/md/raid5.c get_active_stripe+0x683/0x7a0 [raid456]()
Shouldn't md2 have automatically failed? Shouldn't writes immediately
error out instead of pretending to complete?
Joel
next prev parent reply other threads:[~2013-03-14 22:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 1:33 RAID 0 of Two RAID 5s Stays Up When Component RAID fails Joel Young
2013-03-14 3:21 ` Chris Murphy
2013-03-14 4:02 ` Joel Young
2013-03-14 4:03 ` Joel Young
2013-03-14 18:09 ` Chris Murphy
2013-03-14 22:13 ` Joel Young [this message]
2013-03-18 23:57 ` Joel Young
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=loom.20130314T215046-573@post.gmane.org \
--to=jdy@cryregarder.com \
--cc=linux-raid@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