Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: How do I get rid of old device?
Date: Wed, 16 Jan 2008 19:35:41 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0801161935020.9869@p34.internal.lan> (raw)
In-Reply-To: <18318.36828.106749.497307@notabene.brown>



On Thu, 17 Jan 2008, Neil Brown wrote:

> On Wednesday January 16, jpiszcz@lucidpixels.com wrote:
>> p34:~# mdadm /dev/md3 --zero-superblock
>> p34:~# mdadm --examine --scan
>> ARRAY /dev/md0 level=raid1 num-devices=2
>> UUID=f463057c:9a696419:3bcb794a:7aaa12b2
>> ARRAY /dev/md1 level=raid1 num-devices=2
>> UUID=98e4948c:c6685f82:e082fd95:e7f45529
>> ARRAY /dev/md2 level=raid1 num-devices=2
>> UUID=330c9879:73af7d3e:57f4c139:f9191788
>> ARRAY /dev/md3 level=raid0 num-devices=10
>> UUID=6dc12c36:b3517ff9:083fb634:68e9eb49
>> p34:~#
>>
>> I cannot seem to get rid of /dev/md3, its almost as if there is a piece of
>> it on the root (2) disks or reference to it?
>>
>> I also dd'd the other 10 disks (non-root) and /dev/md3 persists.
>
> You don't zero the superblock on the array device, because the array
> device does not have a superblock.  The component devices have the
> superblock.
>
> So
>  mdadm --zero-superblock /dev/sd*
> or whatever.
> Maybe
>  mdadm --examine --scan -v
>
> then get the list of devices it found for the array you want to kill,
> and  --zero-superblock that list.
>
> NeilBrown
>

Thanks, will keep this in mind for the future-- I just checked and the 
dd's have finished and there is no longer a /dev/md3, but mdadm 
--zero-superblock /dev/sd[c-l] would have been much easier.

Justin.

      reply	other threads:[~2008-01-17  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 23:09 How do I get rid of old device? Justin Piszcz
2008-01-16 23:13 ` Justin Piszcz
2008-01-16 23:14 ` Neil Brown
2008-01-17  0:35   ` Justin Piszcz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0801161935020.9869@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox