linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 100% disk usage reported by "df", 60% disk usage reported by "btrfs fi usage" - this breaks userspace behaviour
Date: Sat, 07 Dec 2019 10:54:06 +0900	[thread overview]
Message-ID: <5b5f51dacbb44eb0318c136564c19364@wpkg.org> (raw)
In-Reply-To: <CAJCQCtTB8oKnG0kAkYC_wCvVE1WBYHrAYhWoZR5zKsmGgut6AA@mail.gmail.com>

On 2019-12-07 10:05, Chris Murphy wrote:
> On Fri, Dec 6, 2019 at 5:47 PM Tomasz Chmielewski <mangoo@wpkg.org> 
> wrote:
>> 
>> On 2019-12-06 12:54, Chris Murphy wrote:
>> 
>> > What version of coreutils?
>> 
>> This is Ubuntu 18.04 LTS, with coreutils 8.28.
>> 
>> 
>> > Maybe attach a strace of df? (I'm not sure of the list attach size
>> > limit but it's preferred, but something like a pastebin is OK also)
>> 
>> "Unfortunately" I did run a balance, which "recovered" the space for 
>> df.
> 
> Still an interesting data point.

Well, there is some crap there... it went read-only.

[164625.770369] BTRFS info (device nvme1n1): found 683 extents
[164630.127647] BTRFS info (device nvme1n1): relocating block group 
345766887424 flags data
[164650.186985] BTRFS info (device nvme1n1): found 4268 extents
[164658.075685] BTRFS info (device nvme1n1): found 4266 extents
[164663.979192] BTRFS info (device nvme1n1): relocating block group 
344693145600 flags data
[164686.646073] BTRFS info (device nvme1n1): found 3721 extents
[164696.815655] BTRFS: error (device nvme1n1) in 
btrfs_drop_snapshot:5402: errno=-4 unknown
[164696.821925] BTRFS info (device nvme1n1): forced readonly
[164696.834151] BTRFS warning (device nvme1n1): could not allocate space 
for delete; will truncate on mount
[164696.834162] BTRFS info (device nvme1n1): balance: ended with status: 
-4
[164697.468475] BTRFS info (device nvme1n1): delayed_refs has NO entry


Tomasz Chmielewski
https://lxadm.com

      reply	other threads:[~2019-12-07  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  2:04 100% disk usage reported by "df", 60% disk usage reported by "btrfs fi usage" - this breaks userspace behaviour Tomasz Chmielewski
2019-12-06  3:54 ` Chris Murphy
2019-12-07  0:47   ` Tomasz Chmielewski
2019-12-07  1:05     ` Chris Murphy
2019-12-07  1:54       ` Tomasz Chmielewski [this message]

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=5b5f51dacbb44eb0318c136564c19364@wpkg.org \
    --to=mangoo@wpkg.org \
    --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 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).