linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: Stephen Lee <splee@plexio.com>
Cc: Raid <linux-raid@vger.kernel.org>
Subject: Re: RAID-1 does not rebuild after hot-add
Date: Tue, 05 Aug 2003 00:34:22 +0800	[thread overview]
Message-ID: <3F2E8B0E.6060007@shaolinmicro.com> (raw)
In-Reply-To: 1059929757.6751.60.camel@ralph.plexio.private

>
>
>>[root@www2 root]# cat /proc/mdstat
>>Personalities : [raid1]
>>read_ahead 1024 sectors
>>md0 : active raid1 sdb1[1] sda1[0]
>>      104320 blocks [2/2] [UU]
>>     
>>md1 : active raid1 sdb2[1] sda2[0]
>>      1052160 blocks [2/2] [UU]
>>     
>>md2 : active raid1 sdb3[1]
>>      3076352 blocks [2/1] [_U]
>>     
>>md3 : active raid1 sdb5[1]
>>      1052160 blocks [2/1] [_U]
>>     
>>md4 : active raid1 sdb6[1]
>>      12635008 blocks [2/1] [_U]
>>    
>>
><snip>
>
>Did you try:
>mdadm /dev/md2 -a /dev/sda3
>mdadm /dev/md3 -a /dev/sda5
>mdadm /dev/md4 -a /dev/sda6
>  
>
Already tried. I notice this problem happens in Redhat distributions 
since 7.3 to 9 . When attempting to hot add disks, it doesn't rebuild. I 
am wondering are there ioctls that I can call the md to start rebuild 
without having to wait for an auto rebuild action.

My previous experience is the only way to fix is to freshly mkraid the 
array. I guess something wrong with the super block.

If I can manually dd a superblock into the new disks, I am fool the md 
driver to make it look like already in the array. However, I think I 
have to edit the event count and reboot the machine. Please suggests 
directions.

regards,
David Chow

>If this doesn't work then what are the exact error messages?
>
>Stephen
>  
>


  reply	other threads:[~2003-08-04 16:34 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 [this message]
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
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=3F2E8B0E.6060007@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=splee@plexio.com \
    /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).