All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Raiber <martin@urbackup.org>
To: Chris Murphy <lists@colorremedies.com>,
	Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Qu Wenruo <quwenruo.btrfs@gmx.com>
Subject: Re: df shows no available space in 5.4.1
Date: Fri, 6 Dec 2019 22:51:42 +0000	[thread overview]
Message-ID: <0102016edd69655b-b6d07bce-6036-4add-aa0c-f91b57e78ee5-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <CAJCQCtTMCQBU98hYdzizMsxajB+6cmxYs5CKmNVDh4D9YZgfEg@mail.gmail.com>

On 06.12.2019 23:35 Chris Murphy wrote:
> On Fri, Dec 6, 2019 at 2:26 PM Martin Raiber <martin@urbackup.org> wrote:
>> Hi,
>>
>> with kernel 5.4.1 I have the problem that df shows 100% space used. I
>> can still write to the btrfs volume, but my software looks at the
>> available space and starts deleting stuff if statfs() says there is a
>> low amount of available space.
> This is the second bug like this reported in as many days against 5.4.1.
>
> Does this happen with an older kernel? Any 5.3 kernel or 5.2.15+ or
> any 5.1 kernel? Or heck, even 5.4? :P

Sorry, didn't see the other thread. Looks like the same issue.
Unfortunately, I was previously using 4.19.x, so I can't pinpoint it. I
think it did not occur when I was testing 5.4-rc7, but it does
(randomly?) take a few days of runtime to start occuring, so it could
have just not occurred then.

>> # df -h
>> Filesystem                                            Size  Used Avail
>> Use% Mounted on
>> ...
>> /dev/loop0                                            7.4T  623G     0
>> 100% /media/backup
>> ...
>>
>> statfs("/media/backup", {f_type=BTRFS_SUPER_MAGIC, f_bsize=4096,
>> f_blocks=1985810876, f_bfree=1822074245, f_bavail=0, f_files=0,
>> f_ffree=0, f_fsid={val=[3667078581, 2813298474]}, f_namelen=255,
>> f_frsize=4096, f_flags=ST_VALID|ST_NOATIME}) = 0
>
> f_bavail=0 seems wrong to me.
>
> What distro and what version of coreutils?

It's debian stretch coreutils 8.26-3, glibc 2.29-3. But that's an
excerpt of the strace output so that shouldn't matter.

Thanks!

>
> It's the same questions for Tomasz in yesterday's thread with similar subject.
>
> --
> Chris Murphy



  reply	other threads:[~2019-12-06 22:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 21:26 df shows no available space in 5.4.1 Martin Raiber
2019-12-06 22:35 ` Chris Murphy
2019-12-06 22:51   ` Martin Raiber [this message]
2019-12-08 18:12   ` Zygo Blaxell
2019-12-07  7:28 ` Qu Wenruo
2019-12-09 18:56   ` Martin Raiber
2019-12-09 19:26     ` Martin Raiber
2019-12-10  0:52     ` Qu Wenruo
2019-12-10  1:19       ` Qu Wenruo
2019-12-11 13:11         ` Martin Raiber
2019-12-16  5:04           ` Qu Wenruo
2019-12-13 16:02 ` David Sterba
2019-12-13 20:03 ` Chris Murphy

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=0102016edd69655b-b6d07bce-6036-4add-aa0c-f91b57e78ee5-000000@eu-west-1.amazonses.com \
    --to=martin@urbackup.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=mangoo@wpkg.org \
    --cc=quwenruo.btrfs@gmx.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.