From: Hubert Kario <hka@qbs.com.pl>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Interpreting Output of "btrfs fi show"
Date: Mon, 30 Apr 2012 19:03:58 +0200 [thread overview]
Message-ID: <1530119.sl3296EQTA@bursa01> (raw)
In-Reply-To: <pan.2012.04.29.04.15.24@cox.net>
On Sunday 29 of April 2012 04:15:24 Duncan wrote:
> > Still, a "zero-superblock" option would be useful for the btrfs too=
l.
> > I'll see what I can do about this.
>=20
> Yes, indeed. Particularly since various bits of btrfs functionality=20
> depend on scanning for filesystems (presumably their superblocks), an=
d=20
> output like that in the OP can be confusing indeed, as well as=20
> potentially dangerous in recovery situations, where the wrong one mig=
ht=20
> be activated by accident. (FWIW, there's an mdadm --zero-superblock=20
> option. I should take note of this thread and be sure I use it when =
next=20
> I redo my layouts, probably when I switch some of them to btrfs inste=
ad,=20
> tho that's going to be a bit as I'm waiting for N-way-mirroring, aka=20
> proper raid1 mode, not the 2-way-only-mirroring that btrfs calls raid=
1=20
> mode currently.)
mdadm --zero-superblock removes MD superblock, it doesn't modify the da=
ta part=20
of the partition, it just zeroes the MD metadata.
Regards,
--=20
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawer=F3w 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
--
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:[~2012-04-30 17:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 2:34 Interpreting Output of "btrfs fi show" Thomas Rohwer
2012-04-26 8:34 ` Bart Noordervliet
2012-04-26 9:06 ` Thomas Rohwer
2012-04-26 10:04 ` Bart Noordervliet
2012-04-26 10:14 ` Thomas Rohwer
2012-04-26 11:11 ` Helmut Hullen
2012-04-26 11:53 ` David Sterba
2012-04-26 13:59 ` Helmut Hullen
2012-04-26 20:54 ` Duncan
2012-04-28 16:42 ` Hubert Kario
2012-04-29 4:15 ` Duncan
2012-04-30 17:03 ` Hubert Kario [this message]
2012-04-29 18:34 ` Hugo Mills
2012-04-29 6:13 ` Martin Steigerwald
2012-04-30 17:10 ` Hubert Kario
2012-04-30 18:12 ` Mike Fleetwood
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=1530119.sl3296EQTA@bursa01 \
--to=hka@qbs.com.pl \
--cc=1i5t5.duncan@cox.net \
--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).