From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: wrong values in "df" and "btrfs filesystem df"
Date: 11 Apr 2011 11:06:00 +0200 [thread overview]
Message-ID: <BjeBqvFy1uB@helmut.hullen.de> (raw)
In-Reply-To: <chaz20110411072946.GA5587@seebyte.com>
Hallo, Stephane,
Du meintest am 11.04.11:
> What's the implication of having disks of differing sizes? Does
> that mean that the extra space on larger disks is lost?
Seems to work.
I've tried:
/dev/sda 140 GByte
/dev/sdb 140 GByte
/dev/sdc 70 GByte
mkfs.btrfs -d raid0 -m raid1 /dev/sdb1 /dev/sdc1
mounted, more than 140 GByte free
Filled with more than 140 GByte (/dev/sdc1 was full to the brim)
btrfs device add /dev/sda1 ...
btrfs filesystem balance ...
Needed many hours, but then more than 210 GByte were usable.
Filled up to about 220 GByte; /dev/sdc1 was again full to the brim
btrfs device delete /dev/sdc1
umount
mount
All looks as expected, only the 2 bigger devices are seen, and they
contain the expected files.
And that looks good: my major interest in btrfs is working in that way -
adding a bigger device, deleting a smaller device.
Kernel 2.6.38.1
btrfs from november 2010
Only the values shown with "df" and "btrfs filesystem df" need getting
used to; maybe "available" has to be seen as "at least available".
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-04-11 9:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-09 6:25 wrong values in "df" and "btrfs filesystem df" Helmut Hullen
2011-04-09 9:11 ` Hugo Mills
2011-04-09 9:46 ` Stephane Chazelas
2011-04-09 12:28 ` Helmut Hullen
2011-04-09 16:36 ` Calvin Walton
2011-04-09 17:05 ` Helmut Hullen
2011-04-09 17:26 ` Calvin Walton
2011-04-09 18:15 ` Helmut Hullen
2011-04-09 19:35 ` Peter Stuge
2011-04-09 20:38 ` Hugo Mills
2011-04-10 10:13 ` Miao Xie
2011-04-11 7:29 ` Stephane Chazelas
2011-04-11 7:56 ` Arne Jansen
2011-04-11 9:06 ` Helmut Hullen [this message]
2011-04-12 7:22 ` Miao Xie
2011-04-12 8:17 ` Stephane Chazelas
2011-04-13 5:35 ` Miao Xie
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=BjeBqvFy1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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).