All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: ENOSPC on mostly empty file system
Date: Tue, 9 Sep 2014 22:23:33 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.09.09.22.23.33@googlemail.com> (raw)
In-Reply-To: 10095560.XRujO0W0CE@wuerfel

On Tue, 09 Sep 2014 23:49:10 +0200, Arnd Bergmann wrote:

> Label: none  uuid: 1d88cccb-3d0e-42d9-8252-a226dc5c2e47
>         Total devices 1 FS bytes used 8.79GB
>         devid    1 size 67.14GB used 67.14GB path /dev/sdc6
                          ^^^^^^^^^^^^^^^^^^^^ *ding ding ding*

The term "used" is confusing here and really should be called
"allocated", since it's more than the number of actually used
bytes. Note that df shows that you "have" ~66GB data and ~1GB
metadata (giving approx. ~67GB), despite the fact that of those
65GB data allocated only ~8GB are actually used.

However all these reserved data chunks are preventing the metadata
space from expanding, which is pretty full:
Metadata, DUP: total=1.00GB, used=799.54MB

Here "total" also should be "allocated/reserved" and is 1GB, but
btrfs feels it's necessary to allocate a new metadata chunk
(which would also increase "total") and fails.

Running balance with -dusage=x will garbage-collect the reserved but
mostly-empty data chunks with "up to x" percent actual usage.

-h


      parent reply	other threads:[~2014-09-09 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09 14:29 ENOSPC on mostly empty file system Arnd Bergmann
2014-09-09 15:06 ` Holger Hoffstätte
2014-09-09 15:12   ` Holger Hoffstätte
2014-09-09 18:18 ` Arnd Bergmann
2014-09-09 19:49   ` Clemens Eisserer
2014-09-09 19:56     ` Hugo Mills
2014-09-09 21:49     ` Arnd Bergmann
2014-09-09 21:57       ` Hugo Mills
2014-09-09 22:11         ` Roman Mamedov
2014-09-09 22:12         ` Arnd Bergmann
2014-09-09 22:23       ` Holger Hoffstätte [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=pan.2014.09.09.22.23.33@googlemail.com \
    --to=holger.hoffstaette@googlemail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.