From: Joel Young <jdy@cryregarder.com>
To: linux-raid@vger.kernel.org
Subject: RAID 0 of Two RAID 5s Stays Up When Component RAID fails
Date: Thu, 14 Mar 2013 01:33:52 +0000 (UTC) [thread overview]
Message-ID: <loom.20130314T022616-853@post.gmane.org> (raw)
What should the output be for the following sequence:
dd if=/dev/zero of=i1 bs=1M count=100
dd if=/dev/zero of=i2 bs=1M count=100
dd if=/dev/zero of=i3 bs=1M count=100
dd if=/dev/zero of=i4 bs=1M count=100
dd if=/dev/zero of=i5 bs=1M count=100
dd if=/dev/zero of=i6 bs=1M count=100
losetup /dev/loop1 i1
losetup /dev/loop2 i2
losetup /dev/loop3 i3
losetup /dev/loop4 i4
losetup /dev/loop5 i5
losetup /dev/loop6 i6
mdadm --create /dev/md0 --level=5 --raid-devices=3 \
/dev/loop1 /dev/loop2 /dev/loop3
mdadm --create /dev/md1 --level=5 --raid-devices=3 \
/dev/loop4 /dev/loop5 /dev/loop6
mdadm --create /dev/md2 --level=0 --raid-devices=2 \
/dev/md0 /dev/md1
mdadm /dev/md0 --fail /dev/loop0
mdadm /dev/md0 --fail /dev/loop1
mdadm --detail /dev/md0
mdadm --detail /dev/md2
dd if=/dev/zero of=/dev/md2 bs=1M
Shouldn't /dev/md2 be failed at this point? Shouldn't the
dd get an error? No error was reported. /dev/md2 is writable.
Where are the writes going?
What am I missing?
This is running on fedora 18. We saw the problem with production arrays on
fedora 17.
mdadm version: mdadm - v3.2.6 - 25th October 2012
kernel: 3.7.9-201.fc18.x86_64
Thanks,
Joel
next reply other threads:[~2013-03-14 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 1:33 Joel Young [this message]
2013-03-14 3:21 ` RAID 0 of Two RAID 5s Stays Up When Component RAID fails 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
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.20130314T022616-853@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