Re: MD or MDADM bug?

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

 



On Friday September 2, dstrang@xxxxxxxxxxxxxx wrote:
> Neil Brown wrote:
> > On Friday September 2, dstrang@xxxxxxxxxxxxxx wrote:
> > > >
> > > > Can you run that with '-v' for me?
> > > 
> > > mdadm: looking for devices for /dev/md0
> > > mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
> > > mdadm: /dev/sdb is identified as a member of /dev/md0, slot 1.
> > > mdadm: /dev/sdc is identified as a member of /dev/md0, slot 2.
> > ...
> > 
> > and just for completeness:
> > 
> >  mdadm -E /dev/sdm /dev/sdaa 
> > 
> 
> -(root@abyss)-(~)- # mdadm -E /dev/sdm /dev/sdaa

Thanks.

Looks like --assemble is not going to work any more for you.
However you should be able to recreate the array:

 mdadm -C /dev/md0 -l5 -n28 -c 128 --name=md/md0 -p la  /dev/sd[a-l] missing /dev/sd[n-z] /dev/sda[ab]

should get it right. (You did deliberately choose left-asymmetric I assume).

I've put a note on my todo list to test out these failure modes
and make sure it does the right thing next time.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[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