From: Peter Rabbitson <rabbit+list@rabbit.us>
To: linux-raid@vger.kernel.org
Subject: mdraid10 regression in 2.6.27.4 (possibly earlier)
Date: Sun, 02 Nov 2008 12:27:59 +0100 [thread overview]
Message-ID: <490D8EBF.8050400@rabbit.us> (raw)
[-- Attachment #1: Type: text/plain, Size: 394 bytes --]
Hi,
Some weeks ago I upgraded from 2.6.23 to 2.6.27.4. After a failed hard
drive I realized that re-adding drives to a degraded raid10 no longer
works (it adds the drive as a spare and never starts a resync). Booting
back into the old .23 kernel allowed me to complete and resync the array
as usual. Attached find a test case reliably failing on vanilla 2.6.27.4
with no patches.
Thank you
[-- Attachment #2: raid_test_2.6.27.4 --]
[-- Type: text/plain, Size: 511 bytes --]
#!/bin/bash
set -e
[ -e /dev/loop1 ] || modprobe loop
for i in 1 2 3 4; do
dd if=/dev/zero of=blkloop_$i bs=10M count=1
losetup /dev/loop$i blkloop_$i
done
mdadm -C /dev/md7 -n 4 -l 10 -p f3 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4
# wait for sync
sleep 2
mdadm -f /dev/md7 /dev/loop1
mdadm -r /dev/md7 /dev/loop1
mdadm -a /dev/md7 /dev/loop1
for i in 1 2 3 4; do
cat /proc/mdstat
sleep 2
done
mdadm -S /dev/md7
for i in 1 2 3 4; do
losetup -d /dev/loop$i
rm blkloop_$i
done
next reply other threads:[~2008-11-02 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 11:27 Peter Rabbitson [this message]
2008-11-02 17:37 ` md raid10 regression in 2.6.27.4 (possibly earlier) Thomas Backlund
2008-11-02 23:51 ` Thomas Backlund
2008-11-03 18:09 ` Thomas Backlund
2008-11-03 18:28 ` Justin Piszcz
2008-11-05 23:30 ` md raid10 regression in 2.6.27.4 (possibly earlier) BISECTED Thomas Backlund
2008-11-06 6:18 ` Neil Brown
2008-11-06 9:23 ` Thomas Backlund
-- strict thread matches above, loose matches on Subject: below --
2008-11-02 17:33 mdraid10 regression in 2.6.27.4 (possibly earlier) George Spelvin
2008-11-03 8:30 ` George Spelvin
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=490D8EBF.8050400@rabbit.us \
--to=rabbit+list@rabbit.us \
--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;
as well as URLs for NNTP newsgroup(s).