On 30 April 2012 18:10, Hubert Kario <h...@qbs.com.pl> wrote: > 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 <troh...@ennit.de> wrote: >> > >> As for the two filesystems shown in btrfs fi show... I have no clue >> > >> what that is about. Did you maybe make a mistake to create a btrfs >> > >> filesystem on the whole disk at first? >> > > >> > > That is possible. But afterwards I certainly repartioned the device >> > > and created a btrfs filesystem on /dev/sda1. Maybe this info is only >> > > in the partition table? I understand that I should avoid mounting >> > > /dev/sda in this situation. >> > >> > 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 would >> > go about erasing the stale superblock and whether it is safe to do so >> > I can't say though. >> >> There is the command wipefs. Whether its safe to use here I do not know. I >> wouldn´t try without a backup. > > Sorry, but I'm unable to find it. Is it a `btrfs` tool option or is it a > standalone application (in similar form as is the `btrfs-zero-log`)?
Google is your friend. wipefs is part of util-linux from 2.17, circa Jan-2010. Mike -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
