From: Eric Sandeen <sandeen@redhat.com>
To: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [bug] df reports wrong Size and Avail on raid1, 3.18rc2
Date: Tue, 28 Oct 2014 21:26:08 -0500 [thread overview]
Message-ID: <54505040.6050004@redhat.com> (raw)
In-Reply-To: <B3CDA0F0-14F7-4539-B7FF-B2D2E5F7CAF2@colorremedies.com>
On 10/28/14 9:19 PM, Chris Murphy wrote:
> 3.18.0-0.rc2.git1.1.fc22.x86_64
> btrfs-progs-3.17-1.fc21.x86_64
>
> # btrfs fi show /mnt
> Label: 'btrfs1' uuid: 0f1c615f-30a0-4166-8a3c-987849551513
> Total devices 2 FS bytes used 233.54GiB
> devid 1 size 465.76GiB used 236.03GiB path /dev/sdb
> devid 2 size 298.09GiB used 236.03GiB path /dev/sdc
>
> # df -h /mnt
> Filesystem Size Used Avail Use% Mounted on
> /dev/sdb 382G 234G 65G 79% /mnt
>
>
> a. df -h should report Size as 298GiB rather than as 382GiB.
> Because this is 2 device raid1, the limiting factor is devid 2 @ 298GiB.
>
> b. df -h should report Avail as 62GiB or less, rather than as 65GiB.
> 298.09 - 236.03 = 62.06
Is there an fstest for btrfs disk space reporting?
ext2/3/4 used to keep getting "overhead" wrong for various filesystem
types ... until we wrote a regression test.
Just sayin' :)
-Eric
next prev parent reply other threads:[~2014-10-29 2:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 2:19 [bug] df reports wrong Size and Avail on raid1, 3.18rc2 Chris Murphy
2014-10-29 2:26 ` Eric Sandeen [this message]
2014-12-09 11:20 ` [PATCH] Btrfs: get more accurate output in fd command Dongsheng Yang
2014-12-09 18:47 ` Goffredo Baroncelli
2014-12-10 1:08 ` Dongsheng Yang
2014-12-10 10:53 ` Robert White
2014-12-10 13:21 ` Duncan
2014-12-10 15:02 ` Dongsheng Yang
2014-12-10 19:05 ` Goffredo Baroncelli
2014-12-11 8:23 ` Dongsheng Yang
2014-12-11 3:53 ` Duncan
2014-12-11 8:25 ` Dongsheng Yang
2014-12-10 20:36 ` Robert White
2014-12-10 21:03 ` Goffredo Baroncelli
2014-12-10 14:51 ` Dongsheng Yang
2014-12-10 18:25 ` Goffredo Baroncelli
2014-12-11 8:28 ` Dongsheng Yang
2014-12-10 13:59 ` Shriramana Sharma
2014-12-10 14:56 ` Dongsheng Yang
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=54505040.6050004@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.