Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: Tomasz Chmielewski <tch@virtall.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: no space left, metadata usage almost full?
Date: Wed, 18 Dec 2013 12:46:52 +0000	[thread overview]
Message-ID: <20131218124652.GL11281@carfax.org.uk> (raw)
In-Reply-To: <20131218213728.07d47dd5@virtall.com>

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

On Wed, Dec 18, 2013 at 09:37:28PM +0900, Tomasz Chmielewski wrote:
> I have a btrfs filesystem which has plenty of free space left, yet it's
> hitting out of space regularly.
> 
> Here is how it looks like:
> 
> # btrfs fi df /home
> Data, RAID1: total=2.51TiB, used=1.58TiB
> System, RAID1: total=32.00MiB, used=372.00KiB
> Metadata, RAID1: total=48.00GiB, used=47.23GiB
> 
> 
> What I read from it, is we're almost full on metadata usage, and that
> might be causing out of space issues.

   This is highly likely.

> Reading past posts on this group, I can see it's recommended to run
> this if I hit out of space and the fs is low on metadata space:
> 
> # btrfs fi balance start -dusage=5 /home
> 
> Is it really the only workaround? Shouldn't the filesystem be more
> intelligent and be able to grab some more metadata space if it's
> running low?

   Currently, yes, it is the only approach.

   The automatic reclamation of unused chunks (or barely-used chunks)
is on the projects list. Nobody's got round to implementing it yet.

> I'd appreciate some clarifications on this (FYI, it was running
> 3.11.4, upgraded to the latest rc now).

   Hope the above helps,
   Hugo.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
      --- If it's December 1941 in Casablanca,  what time is it ---      
                              in New York?                               

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-12-18 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 12:37 no space left, metadata usage almost full? Tomasz Chmielewski
2013-12-18 12:46 ` Hugo Mills [this message]
2013-12-18 14:54   ` Tomasz Chmielewski
2013-12-18 15:11     ` Hugo Mills

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=20131218124652.GL11281@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tch@virtall.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