From: minskey guo <chaohong_guo@linux.intel.com>
To: "J. David Beutel" <list@getsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 still recognized after being overwritten by md raid1
Date: Tue, 08 Jun 2010 09:29:00 +0800 [thread overview]
Message-ID: <4C0D9CDC.5010307@linux.intel.com> (raw)
In-Reply-To: <4C0CB7FF.2080405@getsu.com>
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.
-minskey
> Details: after installing on btrfs for the first time, I created a btrfs
> raid1 in Fedora 13 on sda7 sdb7. Then, while reinstalling Fedora 13 from
> DVD, I created an md raid1 on those partitions, containing / type ext4.
> After booting onto that /, btrfs is still recognized on sda7, but sda7
> is also in md7, which is mounted on / as type ext4:
>
> [root@pikake jdb]# cat /proc/mdstat
> Personalities : [raid1]
> md127 : active (auto-read-only) raid1 sdb5[1] sda5[0]
> 204788 blocks super 1.0 [2/2] [UU]
>
> md8 : active raid1 sda8[0] sdb8[1]
> 218100 blocks super 1.0 [2/2] [UU]
>
> md7 : active raid1 sda7[0] sdb7[1]
> 48820156 blocks super 1.1 [2/2] [UU]
> bitmap: 1/1 pages [4KB], 65536KB chunk
>
> md3 : active raid1 sda3[0] sdb3[1]
> 12287936 blocks [2/2] [UU]
>
> unused devices: <none>
> [root@pikake jdb]# btrfs-show
> failed to read /dev/sdf
> failed to read /dev/sde
> failed to read /dev/sdd
> failed to read /dev/sdc
> failed to read /dev/sr0
> Label: none uuid: 3257ab1a-45de-43d3-bd84-a01ca93d0296
> Total devices 1 FS bytes used 7.71GB
> devid 1 size 48.83GB used 14.54GB path /dev/sda6
>
> Label: none uuid: c25ab51a-9fec-4e67-a5d8-4968e7d2e5e8
> Total devices 2 FS bytes used 7.69GB
> devid 1 size 46.56GB used 11.40GB path /dev/sda7
> *** Some devices missing
>
> Btrfs Btrfs v0.19
> [root@pikake jdb]# mount
> /dev/md7 on / type ext4 (rw)
> proc on /proc type proc (rw)
> sysfs on /sys type sysfs (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> tmpfs on /dev/shm type tmpfs
> (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
> /dev/md8 on /boot type ext4 (rw)
> none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
> sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
> gvfs-fuse-daemon on /home/jdb/.gvfs type fuse.gvfs-fuse-daemon
> (rw,nosuid,nodev,user=jdb)
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-08 1:29 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 [this message]
2010-06-08 9:18 ` J. David Beutel
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=4C0D9CDC.5010307@linux.intel.com \
--to=chaohong_guo@linux.intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@getsu.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.