From: Hugo Mills <hugo@carfax.org.uk>
To: Leonidas Spyropoulos <artafinde@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs balance on single device
Date: Sun, 15 Dec 2013 20:24:56 +0000 [thread overview]
Message-ID: <20131215202456.GA11281@carfax.org.uk> (raw)
In-Reply-To: <CAAeznTpG6A7ygKg1AUx_pAMs_SNwG4a4C5gHPeT+HcKRsD+TWA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
On Sun, Dec 15, 2013 at 08:20:19PM +0000, Leonidas Spyropoulos wrote:
> Hey all,
>
> Just did a btrfs balance on a single device. Before the balance
> operation here is the df result:
>
> inglor@tiamat ~$ btrfs fi df /home
> Data: total=19.19GB, used=9.34GB
> System, DUP: total=32.00MB, used=4.00KB
> Metadata, DUP: total=896.00MB, used=227.98MB
>
> Then I issues a balance operation relocating the chunks across a single device:
> inglor@tiamat ~$ sudo btrfs fi balance /home
> [sudo] password for inglor:
> Done, had to relocate 28 out of 28 chunks
>
> After I did another df:
> inglor@tiamat ~$ btrfs fi df /home
> Data: total=10.00GB, used=9.34GB
> System, DUP: total=32.00MB, used=4.00KB
> Metadata, DUP: total=384.00MB, used=226.80MB
>
> Anyone can explain me the Data row of the above output ? It used to be
> 19.19GB and now it's 10.00GB. It's like the partition shrunk!? The
> balance operation finished without issues.
It freed up some of the unused data chunks, returning them to the
unallocated space on the device.
> Here's some other information:
>
> inglor@tiamat ~$ sudo btrfs filesystem show
> Label: 'home' uuid: 458c70e2-7037-4c4d-bba2-3d5288f04510
> Total devices 1 FS bytes used 9.56GB
> devid 1 size 21.00GB used 10.81GB path /dev/sda3
You can see that the filesystem is still the same size as before --
it's just that less of it is allocated.
There's nothing to worry about here -- it's all working as expected.
Hugo.
> Label: none uuid: 699d671b-7064-441d-95ec-c616049fe287
> Total devices 1 FS bytes used 13.94GB
> devid 1 size 20.00GB used 20.00GB path /dev/sda2
>
> Btrfs v0.20-rc1-358-g194aa4a-dirty
> inglor@tiamat ~$ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> /dev/sda2 20971520 15362816 3960288 80% /
> /dev/sda3 22020096 10256168 11375416 48% /home
>
> Thanks,
> Leonidas
>
>
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- If you're not part of the solution, you're part ---
of the precipiate.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-12-15 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 20:20 btrfs balance on single device Leonidas Spyropoulos
2013-12-15 20:24 ` Hugo Mills [this message]
2013-12-15 20:28 ` Leonidas Spyropoulos
2013-12-15 23:28 ` Duncan
2013-12-16 23:22 ` Leonidas Spyropoulos
2013-12-17 5:02 ` Duncan
[not found] ` <CAAeznTpZ6p1_ZR6xy-YGynAJu88jZ_52AQURuxT4qTeEYLOjdg@mail.gmail.com>
2013-12-18 10:44 ` Leonidas Spyropoulos
2013-12-18 11:05 ` Hugo Mills
2013-12-18 11:29 ` Leonidas Spyropoulos
2013-12-19 8:14 ` Leonidas Spyropoulos
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=20131215202456.GA11281@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=artafinde@gmail.com \
--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).