RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".

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

 



On Friday May 16, andrew.henry@xxxxxxxxxx wrote:
> > -----Original Message-----
> >
> > Thanks a lot for the help.  I'll try mdadm --stop as soon as syncing has
> > finished (95% complete now!!!)
> >
> 
> Well, sync finished successfully.
> 
> Mdadm --dtop /dev/md0   # OK
> Mdadm --zero-superblock --force /dev/sda1  # OK
> Mdadm --zero-superblock --force /dev/sdb1  # OK
> 
> These return to prompt without any messages.  If I then run them a second time they complain that the device is not part of an array.  All well and good.
> 
> Mdadm --create --verbose /dev/md0 --level=raid1 --raid-devices=2 /dev/sd[ab]1  # NOT OK.  Complains "already an array" starts a new resync.

I wasn't paying close attention to this thread, so maybe I missed
something significant, but what exactly is the "complaint" you get
here?


> 
> Mdadm --stop /dev/md0  # stops resync :)
> 
> What else is needed?  Am I unable to recreate the array on md0?  Must I choose a new device such as md1?  Or is there another stop to erasing an array?

Why do you feel a need to erase an array?

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