Re: mdadm and raid5 hot-rebuild problem on 2.5.67

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2003-04-16 at 17:29, Neil Brown wrote:
> On Wednesday April 16, neilb@cse.unsw.edu.au wrote:
> > 
> > Ok, this is wrong.  Bigtime.
> > The spare has taken up postion 0 instead of 2.
> > 
> > I cannot immediately see what would be causing this.  The code looks
> > right, but obviously isn't.  I'll try to see if I can reproduce it
> > tomorrow.
> > 
> 
> I haven't managed to reproduce it, but I'm faily sure that I know what
> was happening.  I'll try to figure out the best way to fix it.
> 
> In the mean time, you can avoid the problem by not using raidstart at
> all. 
> Reboot your machine, with raidstart disabled (e.g. move /etc/raidtab
> out of the way) and then us mdadm to start the array.  I think you
> will need "mdadm --assemble --force" to start it.

On a related note, I've recently hacked on rc.sysinit so that it
recognizes /etc/mdadm.conf, in addition to /etc/raidtab.  I've sent to
patch upstream to my vendor of Linux, you can find it at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88785
	Greg

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux