-----Original Message----- From: Neil Brown [mailto:neilb@xxxxxxx] Sent: 19 May 2008 08:10 To: Henry, Andrew Cc: David Greaves; LinuxRaid Subject: RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'". > 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 was saying that the array to be created was already part of an array, but I fixed this now by running dd if=/dev/zero of=/dev/sd[ab] to wipe the whole disk Now when I run: mdadm --create --verbose /dev/md0 --raid-devices=2 --level=raid1 /dev/sd[ab]1 It replies: mdadm: size set to 488383936K mdadm: array /dev/md0 started. However, when I look at mdstat I see the following: [root@k2 ~]# cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb1[1] sda1[0] 488383936 blocks [2/2] [UU] [>....................] resync = 0.0% (187520/488383936) finish=1301.1min speed=6250K/sec unused devices: <none> [root@k2 ~]# Why does it "resync" upon creating a new array? > > 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? Because I created it with version 1.0 superblock and it wasn't getting autodetected by the kernel 2.6.18-53. I want to re-create it with version 0.9 superblock. 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
