From: Hubert Verstraete <hubskml@free.fr>
To: linux-raid@vger.kernel.org
Subject: problems with faulty disks and superblocks 1.0, 1.1 and 1.2
Date: Thu, 31 May 2007 11:20:17 +0200 [thread overview]
Message-ID: <465E9351.2070505@free.fr> (raw)
Hello
I'm having problems with a RAID-1 configuration. I cannot re-add a disk
that I've failed, because each time I do this, the re-added disk is
still seen as failed.
After some investigations, I found that this problem only occur when I
create the RAID array with superblocks 1.0, 1.1 and 1.2.
With the superblock 0.90 I don't encounter this issue.
Here are the commands to easily reproduce the issue
mdadm -C /dev/md_d0 -e 1.0 -l 1 -n 2 -b internal -R /dev/sda /dev/sdb
mdadm /dev/md_d0 -f /dev/sda
mdadm /dev/md_d0 -r /dev/sda
mdadm /dev/md_d0 -a /dev/sda
cat /proc/mdstat
The output of mdstat is:
Personalities : [raid1]
md_d0 : active raid1 sda[0](F) sdb[1]
104849 blocks super 1.2 [2/1] [_U]
bitmap: 0/7 pages [0KB], 8KB chunk
unused devices: <none>
I'm wondering if the way I'm failing and re-adding a disk is correct.
Did I make something wrong?
If I change the superblock to "-e 0.90", there's no problem with this
set of commands.
For now, I found a work-around with superblock 1.0 which consists in
zeroing the superblock before re-adding the disk. But I suppose that
doing so will force a full rebuild of the re-added disk, and I don't
want this, because I'm using write-intent bitmaps.
I'm using mdadm - v2.5.6 on Debian Etch with kernel 2.6.18-4.
Bug or misunderstanding from myself? Any help would be appreciated :)
Thanks
Hubert
next reply other threads:[~2007-05-31 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 9:20 Hubert Verstraete [this message]
2007-06-04 16:43 ` problems with faulty disks and superblocks 1.0, 1.1 and 1.2 Hubert Verstraete
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=465E9351.2070505@free.fr \
--to=hubskml@free.fr \
--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 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.