linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. David Beutel" <list@getsu.com>
To: minskey guo <chaohong_guo@linux.intel.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 still recognized after being overwritten by md raid1
Date: Mon, 07 Jun 2010 23:18:12 -1000	[thread overview]
Message-ID: <4C0E0AD4.3090902@getsu.com> (raw)
In-Reply-To: <4C0D9CDC.5010307@linux.intel.com>

On 06/07/2010 03:29 PM, minskey guo wrote:
> On 06/07/2010 05:12 PM, J. David Beutel wrote:
>> I created an md raid1 on partitions that had a btrfs raid1, but btrfs is
>> still recognized on one of those partitions. (Is it finding some
>> left-over, redundant metadata?) I'm concerned this will confuse me or
>> btrfs in the future. How should I fix this?
>
>
> Seem that btrfs-show checks the 1st superblock only, running the 
> following can zap some part of that superblock,
>
>   dd if=/dev/zero of=/dev/sda7 seek=128 bs=512 count=1
>
> but probably, you need to zap the 2nd superblock as
>
>  dd if=/dev/zero of=/dev/sda7 seek=128k bs=512 count=1
>
>
> In case the block is being used, you can dump that block and
> search "_BHRfS_M" in that block before clear it.


Thanks!  Both of those blocks had "_BHRfS_M".  Zapping them stopped sda7 
from showing up in btrfs-show, while /proc/mdstat is unchanged and / 
still works.

Cheers,
11011011

      reply	other threads:[~2010-06-08  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07  9:12 btrfs raid1 still recognized after being overwritten by md raid1 J. David Beutel
2010-06-08  1:29 ` minskey guo
2010-06-08  9:18   ` J. David Beutel [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=4C0E0AD4.3090902@getsu.com \
    --to=list@getsu.com \
    --cc=chaohong_guo@linux.intel.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).