From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Brown Subject: RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'". Date: Mon, 19 May 2008 16:10:05 +1000 Message-ID: <18481.6589.876469.898266@notabene.brown> References: <3ECBDC05781B3D48ABD520A01ABF2F9B12C53D0880@SE-EX008.groupinfra.com> <482B5600.6040204@dgreaves.com> <3ECBDC05781B3D48ABD520A01ABF2F9B12C5435703@SE-EX008.groupinfra.com> <482C4240.7020202@dgreaves.com> <3ECBDC05781B3D48ABD520A01ABF2F9B12C546FB2B@SE-EX008.groupinfra.com> <3ECBDC05781B3D48ABD520A01ABF2F9B12C54704D3@SE-EX008.groupinfra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: message from Henry, Andrew on Friday May 16 Sender: linux-raid-owner@vger.kernel.org To: "Henry, Andrew" Cc: David Greaves , LinuxRaid List-Id: linux-raid.ids On Friday May 16, andrew.henry@logica.com 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