linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Lee <splee@plexio.com>
To: Raid <linux-raid@vger.kernel.org>
Subject: Re: RAID-1 does not rebuild after hot-add
Date: 03 Aug 2003 09:55:57 -0700	[thread overview]
Message-ID: <1059929757.6751.60.camel@ralph.plexio.private> (raw)
In-Reply-To: <3F2D1FAC.9030905@shaolinmicro.com>

On Sun, 2003-08-03 at 07:43, David Chow wrote:
> Dear Neil,
> 
> A problem on hot adding a disk to an existing RAID array. I was 
> converting my root fs and other fs to md . While I am using the 
> failed-disk and move my data to the new degraded md device, after I hot 
> add a new disk to the md , it doesn't start rebuild. What it looks like 
> in the syslog is as follows (see belows). Looks like the recovery thread 
> dot woken up and finished right away... why? My kernel is 2.4.18-3smp 
> which is a RH7.3 vendor kernel. I'd experience on other 2.4.20 RH 
> kernels which had the same problem. My end up result is to use "mkraid 
> --force" to make it as a new array to enable the resync.  The 
> /proc/mdstat also looks wired which one drive is down "[_U]". In fact, 2 
> drives are actually healthy. I've trid mdadm -manage which produce the 
> same result. I've also tried to dd the partitions to all zero before add 
> but same result. Please give direction, as moving the root to somewhere 
> else and use mkraid to start with is really stupid (my opinion), 
> actually, I've no spare disk to that this time.
> 
> regards,
> David Chow
<snip>

> [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

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

Stephen


  reply	other threads:[~2003-08-03 16:55 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 [this message]
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
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=1059929757.6751.60.camel@ralph.plexio.private \
    --to=splee@plexio.com \
    --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).