From: David Chow <davidchow@shaolinmicro.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-1 does not rebuild after hot-add
Date: Tue, 05 Aug 2003 19:58:39 +0800 [thread overview]
Message-ID: <3F2F9BEF.7080104@shaolinmicro.com> (raw)
In-Reply-To: 16175.21583.621336.653083@gargle.gargle.HOWL
>
>
>>
>>OK, I find out there is a problem in the superblock which is descrbed as
>>follows. The "Total Devices" is wrong. It should be 2 instead of 3. This
>>is probably a bug of the mkraid (from raidtools) which when I created
>>the array with a "failed-disk" in degraded mode. mkraid incorrectly made
>>a wrong superblock even I put "nr-raid-disk 2" and "nr-spare-disks 0" in
>>the raidtab. Ok, the superblock is incorrect, but how can I change the
>>total devices and spare device pramaters without re-initialize the
>>array?
>>
>>
>
>It is actuallt "Active Devices" that is the problem. As this is the
>same as "Raid Devices", it doesn't bother doing a reconstruction.
>
>The following patch adds --update=summaries to mdadm-1.3.0, which
>updates the various summary fields in the superblock (Total, Active,
>Working, Failed, Spare - Devices).
>It is untested but should work.
>If you patch mdadm-1.3.0 and compile it, then
>
> mdadm --assemble /dev/md2 --update=summaries /dev/sda3 /dev/sdb3
>
>then it should update these fields and start the array (you might need
>a --run as well).
>
>Let me know how it goes.
>
>
>
The point is my root is on md2 . I can never reassemble the RAID
devices. This is just the same of using a --force with mkraid of mdadm
with reassemble . There seems no other way to update buggy superblocks
online or even do something with reboot? Can I just modify the field and
reset the machine after a "sync"?
David
next prev parent reply other threads:[~2003-08-05 11:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 14:43 RAID-1 does not rebuild after hot-add David Chow
2003-08-03 16:55 ` Stephen Lee
2003-08-04 16:34 ` David Chow
2003-08-04 17:06 ` Ross Vandegrift
2003-08-04 17:46 ` Paul Clements
2003-08-04 0:38 ` Neil Brown
2003-08-04 16:41 ` David Chow
2003-08-05 2:16 ` Neil Brown
2003-08-05 6:32 ` David Chow
2003-08-05 6:53 ` Neil Brown
2003-08-05 11:58 ` David Chow [this message]
2003-08-06 1:01 ` Neil Brown
2003-08-04 12:41 ` Andrew Rechenberg
2003-08-04 16:32 ` David Chow
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=3F2F9BEF.7080104@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).