All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Confusing output of btrfs fi df
Date: Mon, 28 Apr 2014 01:48:15 +0000 (UTC)	[thread overview]
Message-ID: <pan$bf8bb$295ee5d2$1cf4d367$4ef83ac5@cox.net> (raw)
In-Reply-To: 20140427153726.GA20596@mars

Stefan Malte Schumacher posted on Sun, 27 Apr 2014 17:37:26 +0200 as
excerpted:

> Chris and Duncan: I tried both your suggestions but unfortunately
> without success. Here is the output:
> 
> mars:~ # btrfs balance start -susage=0 -f -v /mnt/btrfs/
> Dumping filters: flags 0xa, state 0x0, force is on
>   SYSTEM (flags 0x2): balancing, usage=0
>   Done, had to relocate 0 out of 2708 chunks
>   
> mars:~ # btrfs fi df /mnt/btrfs/
>   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
> --------------------------------------------
> 
> mars:~ # btrfs balance start -sconvert=raid1,soft -f -v /mnt/btrfs/
> Dumping filters: flags 0xa, state 0x0, force is on
>   SYSTEM (flags 0x300): converting, target=16, soft is on
>   Done, had to relocate 0 out of 2708 chunks
> 
> mars:~ # btrfs fi df /mnt/btrfs/
>   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

OK, this is interesting  It may be that you're reproducing something a 
couple other people saw earlier, but I've never seen here, which might be 
because I tend to do -m<whatever (metadata) and let it handle -s/system 
at the same time, instead of doing -s<whatever> explicitly.

So try this one:

btrfs balance start -musage=0 -v

(-f shouldn't be needed for this one because you're not doing -s 
specifically, and not forcing a lower redundancy level.)

It may or may not free a couple metadata chunks too, but at least here, 
that's /exactly/ what I've used, and it has /never/ failed to cleanup 
that unused system chunk.

If that fails to remove the extra system chunk, then we have a mystery 
indeed.  What's different on your system and why isn't it working?

If it succeeds in removing it, then we have a different and more limited 
bug/mystery.  -s sometimes ignores system chunks it's documented to 
balance, while -m is doing both metadata and system, as expected.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-04-28  1:48 UTC|newest]

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

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='pan$bf8bb$295ee5d2$1cf4d367$4ef83ac5@cox.net' \
    --to=1i5t5.duncan@cox.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.