From: Hubert Kario <hka@qbs.com.pl>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Interpreting Output of "btrfs fi show"
Date: Mon, 30 Apr 2012 19:10:26 +0200 [thread overview]
Message-ID: <4295276.7uL8mlRAJE@bursa01> (raw)
In-Reply-To: <201204290813.48417.Martin@lichtvoll.de>
On Sunday 29 of April 2012 08:13:48 Martin Steigerwald wrote:
> Am Donnerstag, 26. April 2012 schrieb Bart Noordervliet:
> > On Thu, Apr 26, 2012 at 11:06, Thomas Rohwer <trohwer@ennit.de> wro=
te:
> > >> As for the two filesystems shown in btrfs fi show... I have no c=
lue
> > >> what that is about. Did you maybe make a mistake to create a btr=
fs
> > >> filesystem on the whole disk at first?
> > >=20
> > > That is possible. But afterwards I certainly repartioned the devi=
ce
> > > and created a btrfs filesystem on /dev/sda1. Maybe this info is o=
nly
> > > in the partition table? I understand that I should avoid mounting
> > > /dev/sda in this situation.
> >=20
> > Well I think there is a btrfs superblock still present from the
> > full-disk filesystem. Due to the offset of the first partition from
> > the start of the disk, this superblock was not overwritten when you
> > created the filesystem inside the partition. But they very much
> > overlap and the full-disk superblock will probably eventually be
> > overwritten by elements from the partition filesystem. How you woul=
d
> > go about erasing the stale superblock and whether it is safe to do =
so
> > I can't say though.
>=20
> There is the command wipefs. Whether its safe to use here I do not kn=
ow. I
> wouldn=B4t try without a backup.
Sorry, but I'm unable to find it. Is it a `btrfs` tool option or is it =
a=20
standalone application (in similar form as is the `btrfs-zero-log`)?
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:10 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
2012-04-29 18:34 ` Hugo Mills
2012-04-29 6:13 ` Martin Steigerwald
2012-04-30 17:10 ` Hubert Kario [this message]
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=4295276.7uL8mlRAJE@bursa01 \
--to=hka@qbs.com.pl \
--cc=Martin@lichtvoll.de \
--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).