From: Elmar Weber <lists@elmarweber.org>
To: linux-raid@vger.kernel.org
Subject: Raid 1 up after raidhotadd without rebuild
Date: Tue, 14 Nov 2006 10:29:45 +0100 [thread overview]
Message-ID: <45598C89.6080101@elmarweber.org> (raw)
Hello,
I'm trying to rebuild a raid1 array by adding the replacement disk (sda)
to the old one (sdf). I zero'd the new disk (sda) and created the
partition table corresponding to the existing one.
I adapted my raidtab to the new drive node (changed due to other disk
replacement) and now I'm trying to add the new disk, but the raid 1 is
not rebuilding, the newly added disk is marked as U(p) in the mdstat output.
Here's what I do step by step (mdstat output reduced to one raid array,
but the problem exists with every partition used as a raid 1):
# cat /proc/mdstat
md1 : active raid1 sdf1[1]
112728000 blocks [2/1] [_U]
# raidhotadd /dev/md1 /dev/sda1 && cat /proc/mdstat
md1 : active raid1 sda1[1] sdf1[0]
112728000 blocks [2/2] [UU]
Thats it, no resync, nothing. When I do a fsck on the md1 there are
errors en masse. raidtools don't even seem to touch sda1, since when I
create a filesystem with content on it, I can mount it after adding it
to the raid.
Any ideas why this is and how to fix it?
Thanks in advance & ciao,
elm
Here is the entry in the syslog:
==
Nov 15 09:34:46 server md: bind<sda1>
Nov 15 09:34:46 server RAID1 conf printout:
Nov 15 09:34:46 server --- wd:1 rd:2
Nov 15 09:34:46 server disk 0, wo:1, o:1, dev:sda1
Nov 15 09:34:46 server disk 1, wo:0, o:1, dev:sdf1
Nov 15 09:34:46 server md: syncing RAID array md2
Nov 15 09:34:46 server md: minimum _guaranteed_ reconstruction speed:
1000 KB/sec/disc.
Nov 15 09:34:46 server md: using maximum available idle IO bandwidth
(but not more than 200000 KB/sec) for reconstruction.
Nov 15 09:34:46 server md: using 128k window, over a total of 112728000
blocks.
Nov 15 09:34:46 server md: md1: sync done.
Nov 15 09:34:46 server RAID1 conf printout:
Nov 15 09:34:46 server --- wd:2 rd:2
Nov 15 09:34:46 server disk 0, wo:0, o:1, dev:sda1
Nov 15 09:34:46 server disk 1, wo:0, o:1, dev:sdf1
==
Here is the raidtab:
==
raiddev /dev/md1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
persistent-superblock 1
chunk-size 8k
device /dev/sda1
raid-disk 0
device /dev/sdf1
raid-disk 1
==
--
"Religion und Familie sind die beiden größten Feinde des Fortschritts."
(André Gide (1869 - 1951), französischer Schriftsteller)
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2006-11-14 9:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 9:29 Elmar Weber [this message]
2006-11-14 9:35 ` Raid 1 up after raidhotadd without rebuild Neil Brown
2006-11-14 9:46 ` Elmar Weber
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=45598C89.6080101@elmarweber.org \
--to=lists@elmarweber.org \
--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).