From: rabbit@rabbit.us (Peter Rabbitson)
To: linux-raid@vger.kernel.org
Subject: RAID10 Resync fails with specific chunk size and drive sizes (reproducible)
Date: Tue, 20 Feb 2007 06:35:49 -0500 [thread overview]
Message-ID: <20070220113549.GB5584@rabbit.us> (raw)
Hi,
I think I've hit a reproducible bug in the raid 10 driver, tried on two
different machines with kernels 2.6.20 and 2.6.18. This is a script to
simulate the problem:
======================
#!/bin/bash
modprobe loop
for ID in 1 2 3 ; do
echo -n "Creating loopback device $ID... "
dd if=/dev/zero of=dsk${ID}.img bs=512 count=995967
losetup /dev/loop${ID} dsk${ID}.img
echo "done."
done
mdadm -C /dev/md2 -l 10 -n 3 -p o2 -c 2048 /dev/loop1 /dev/loop2 /dev/loop3
echo "Raid device assembled, check /proc/mdstat's output when resync is finished"
======================
This is the output I get in /proc/mdstat after the resync settles:
======================
md2 : active raid10 loop3[2] loop2[3](F) loop1[0]
746496 blocks 2048K chunks 2 offset-copies [3/2] [U_U]
======================
next reply other threads:[~2007-02-20 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 11:35 Peter Rabbitson [this message]
2007-02-20 13:44 ` RAID10 Resync fails with specific chunk size and drive sizes (reproducible) Peter Rabbitson
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=20070220113549.GB5584@rabbit.us \
--to=rabbit@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).