public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Malte Schumacher <s.schumacher@netcologne.de>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: Confusing output of btrfs fi df
Date: Sat, 26 Apr 2014 20:18:27 +0200	[thread overview]
Message-ID: <20140426181827.GA14687@mars> (raw)
In-Reply-To: <20140426143023.GK2391@carfax.org.uk>

> 
>    They're harmless -- it's a side-effect of the way that mkfs works.
> They'll go away if you balance them:
> 
>    btrfs balance start -dprofiles=single -mprofiles=single -sprofiles=single /mountpoint

btrfs refused this command, I had to pass --force to execute it.
It exited with this:Done, had to relocate 2 out of 2710 chunks.

After that btrfs fi df shows the following:

 Data, RAID1: total=2.64TiB, used=2.22TiB
 System, RAID1: total=8.00MiB, used=380.00KiB
>System, single: total=4.00MiB, used=0.00<
 Metadata, RAID1: total=4.00GiB, used=2.94GiB

 
>    btrfs fi label should do this.

I was mainly asking because of this:
https://btrfs.wiki.kernel.org/index.php/UseCases: You can also use
btrfs command.There are currently few limitations: the filesystem has
to be unmounted the filesystem should not have more than one device 

Is this information outdated?

> You might want to look at upgrading to 3.13 or 3.14 kernel, which
> has 6 months or so extra bug fixes in it.

Thanks, going to have a look if openSUSE has anything more recent in
their repositories.

Bye
Stefan


  reply	other threads:[~2014-04-26 18:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26 14:09 Confusing output of btrfs fi df Stefan Malte Schumacher
2014-04-26 14:30 ` Hugo Mills
2014-04-26 18:18   ` Stefan Malte Schumacher [this message]
2014-04-26 21:28     ` Chris Murphy
2014-04-27  1:21       ` Duncan
2014-04-28 12:55       ` Dan van der Ster
  -- strict thread matches above, loose matches on Subject: below --
2014-04-27 15:37 Stefan Malte Schumacher
2014-04-28  1:48 ` Duncan
2014-04-28 11:57 Stefan Malte Schumacher
2014-04-28 12:06 ` Hugo Mills
2014-04-29  1:28 Stefan Malte Schumacher

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=20140426181827.GA14687@mars \
    --to=s.schumacher@netcologne.de \
    --cc=hugo@carfax.org.uk \
    --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