public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Remi Gauvin <remi@georgianit.com>, linux-btrfs@vger.kernel.org
Subject: Re: workaround for buggy GNU df
Date: Wed, 26 Jun 2024 09:40:56 +0300	[thread overview]
Message-ID: <303dee41-7b6e-4a54-be75-acbc3b4da5a5@gmail.com> (raw)
In-Reply-To: <4da3947b-5412-ccaa-527d-d2263da7f36d@georgianit.com>

On 25.06.2024 22:12, Remi Gauvin wrote:
> On 2024-06-25 2:13 p.m., Phillip Susi wrote:
>>> The GNU tool df does not work correctly on btrfs, example:
>>>
>>> root@fex:/test/test/test# df -T phoon.png
>>> Filesystem     Type 1K-blocks     Used Available Use% Mounted on
>>> -              -     67107840 16458828  47946692  26% /test/test
>>>
>>> root@fex:/test/test/test# grep /test /proc/mounts || echo nope
>>> nope
>>>
>>> The mountpoint is wrong, the kernel knows the truth.
>> How did you get this to happen?
>>
> 
> Very easy to replicate.  If you call df with a path, it prints the
> location of the subvolume in the "Mounted As" column.  No other steps
> necessary.
> 
> 

bor@tw:~> df -T /home
Filesystem     Type  1K-blocks     Used Available Use% Mounted on
/dev/sda2      btrfs  39835648 20799988  16982220  56% /home
bor@tw:~> df -T /home/bor
Filesystem     Type  1K-blocks     Used Available Use% Mounted on
/dev/sda2      btrfs  39835648 20799988  16982220  56% /home
bor@tw:~> df -T /home/bor/bin
Filesystem     Type  1K-blocks     Used Available Use% Mounted on
/dev/sda2      btrfs  39835648 20799988  16982220  56% /home
bor@tw:~>



  reply	other threads:[~2024-06-26  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21  6:57 workaround for buggy GNU df Ulli Horlacher
2024-06-25 18:13 ` Phillip Susi
2024-06-25 19:12   ` Remi Gauvin
2024-06-26  6:40     ` Andrei Borzenkov [this message]
2024-09-03 13:26       ` Ulli Horlacher
2026-03-07 11:54 ` Ulli Horlacher

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=303dee41-7b6e-4a54-be75-acbc3b4da5a5@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=remi@georgianit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox