All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rohwer <trohwer@ennit.de>
To: Bart Noordervliet <bart@noordervliet.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Interpreting Output of "btrfs fi show"
Date: Thu, 26 Apr 2012 12:14:48 +0200	[thread overview]
Message-ID: <4F992018.9040006@ennit.de> (raw)
In-Reply-To: <CAGy7UtioPbdjomzuv3phZcF+HShyYKytkOKnAhP+4VGj29Aahg@mail.gmail.com>

> 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.

Ok, that explains it, and it is no problem for me. I was just confused
by the output and thought that this may be related to the "no space"
problem. I just installed kernel 3.3.3, and the problem with "no space"
seems to be gone. Thanks for your quick help.

Sincerely,

Thomas Rohwer

  reply	other threads:[~2012-04-26 10:14 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 [this message]
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
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=4F992018.9040006@ennit.de \
    --to=trohwer@ennit.de \
    --cc=bart@noordervliet.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 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.