linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [bug] df returns 100% used for empty mixed block group filesystem
Date: Thu, 10 Mar 2016 13:33:34 +0500	[thread overview]
Message-ID: <20160310133334.1528bc88@natsu> (raw)
In-Reply-To: <CAJCQCtRzt-BeoW9KNQC3kmBXw8MoydJv7Qy8fu0HmF3hAOgFRQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 679 bytes --]

On Thu, 10 Mar 2016 01:24:44 -0700
Chris Murphy <lists@colorremedies.com> wrote:

> kernel 4.5.0 rc7
> btrfs-progs-4.4.1-1
> 
> Summary: A new empty mixed block group "-M" filesystem shows up as
> 100% full with regular df (gnu coreutils 8.24). Pretty sure this is
> not a regression, but no regression testing done.
> 
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=114281

Just guessing here, but this might be related?

  [PATCH] btrfs: statfs: report zero available if metadata are exhausted
  http://www.spinics.net/lists/linux-btrfs/msg48013.html

Maybe some maths there are wrong in case of a mixed blockgroup filesystem.

-- 
With respect,
Roman

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-03-10  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  8:24 [bug] df returns 100% used for empty mixed block group filesystem Chris Murphy
2016-03-10  8:33 ` Roman Mamedov [this message]
2016-03-10 17:40   ` David Sterba
2016-04-27 22:55     ` David Sterba
2016-04-28  9:58       ` Luis de Bethencourt

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=20160310133334.1528bc88@natsu \
    --to=rm@romanrm.net \
    --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).