@ Raja and Sai Kiran Kanuri - thanks very much for pointing out the faux pas on my part yesterday. This morning after a night's rest I realized where I had messed up :(
On Wednesday 22 Apr 2009, Raja Subramanian wrote: > - Raja > > On Tue, Apr 21, 2009 at 9:31 PM, Arun Khan <[email protected]> wrote: > > However, I don't see any resync between /dev/sdb3 > > to /dev/sda3. Instead, I see sda3[1](S) what is the meaning of S > > against sda3? A single U and the lack of a progress bar in mdstat > > indicates something is not quite right > > .... > > > # cat /proc/mdstat > > Personalities : [raid1] > > md0 : active raid1 sdb3[0] sda3[1](S) > > 89827328 blocks [1/1] [U] > > ^^^^^ > > You created a RAID1 disk set with a single device, > and therefore ended up adding sda3 as a spare disk > for md0. S == spare. Yes, I did not understand the "missing" tag in the man page very well while reading it last night. > Recreate md0 like this: > mdadm --create /dev/md0 -l 1 -n 2 /dev/sdb3 missing I had already planned to do this today but Sai Kiran's method works! (mdadm --grow /dev/md0 --raid-devices=2). /dev/sda3 is now being rebuilt - see below. <transcript> # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb3[0] sda3[2] 89827328 blocks [2/1] [U_] [>....................] recovery = 3.6% (3309632/89827328) finish=39.5min speed=36480K/sec unused devices: <none> </transcript> > Ensure you have backed up your data before playing with > mdadm!! Yes! Thanks for asserting it. The critical data is backed up on a portable hdd. -- Arun Khan _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
