linux-btrfs.vger.kernel.org archive mirror
 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 11:06:47 +0200	[thread overview]
Message-ID: <4F991027.6000903@ennit.de> (raw)
In-Reply-To: <CAGy7UtgsWOmvG16oFTRutFTu5bwq4kT+CQTicqPuYa45YhqUSA@mail.gmail.com>

Hello Bart,

> there's a known regression in 3.3.0 that causes btrfs to report
> out-of-space too early. If you upgrade to 3.3.3 or the latest 3.4 rc
> the problem should be gone.

thanks for the information. I will update my kernel.

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

Sincerely,

Thomas Rohwer

  reply	other threads:[~2012-04-26  9:06 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 [this message]
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
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=4F991027.6000903@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 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).