linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Neil Brown <neilb@suse.de>
Cc: Andre Noll <maan@systemlinux.org>, Jim Paris <jim@jtan.com>,
	linux-raid@vger.kernel.org
Subject: Re: Zeroing multiple superblocks
Date: Mon, 01 Feb 2010 16:22:25 -0500	[thread overview]
Message-ID: <4B674611.2030402@tmr.com> (raw)
In-Reply-To: <20100129233111.5c9cc1d0@notabene>

Neil Brown wrote:
> On Mon, 25 Jan 2010 10:52:21 +0100
> Andre Noll <maan@systemlinux.org> wrote:
>
>   
>> On 15:09, Jim Paris wrote:
>>
>>     
>>> I guess the only way to be fully safe with the current approach is to
>>> do a zero-superblock over and over until it complains.
>>>       
>> mdadm --zero-superblock tries to guess the location of the superblock.
>> If more than one superblock is found, the one with the latest creation
>> time is being zeroed. So yes, the method you describe works and I think
>> it is the most reliable way to remove all superblocks of a device.
>>
>> Maybe we could teach mdadm --zero-superblock to honor the --metadata=x
>> option which would zero-out the region of the device where the
>> version-x superblock is located.
>>     
>
> Latest mdadm has this feature.
> And if --metadata= isn't given, it repeatedly trying to find and zero a
> superblock until no more superblocks can be found.
>   

That would be potentially a bad thing, people do run things like RAID1+5 
and might want to clear on block and save the other, still possibly part 
of a running array, one. I'm not sure that's a safe default behavior.

-- 
Bill Davidsen <davidsen@tmr.com>
  "We can't solve today's problems by using the same thinking we
   used in creating them." - Einstein


  reply	other threads:[~2010-02-01 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 20:09 Zeroing multiple superblocks Jim Paris
2010-01-25  9:52 ` Andre Noll
2010-01-29 12:31   ` Neil Brown
2010-02-01 21:22     ` Bill Davidsen [this message]
2010-02-01 21:44       ` Neil Brown

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=4B674611.2030402@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jim@jtan.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=maan@systemlinux.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;
as well as URLs for NNTP newsgroup(s).