All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Chmielewski <tch@virtall.com>
To: Hugo Mills <hugo@carfax.org.uk>
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 23:54:39 +0900	[thread overview]
Message-ID: <20131218235439.480170e0@virtall.com> (raw)
In-Reply-To: <20131218124652.GL11281@carfax.org.uk>

On Wed, 18 Dec 2013 12:46:52 +0000
Hugo Mills <hugo@carfax.org.uk> wrote:

> > # 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
> > # btrfs fi balance start -dusage=5 /home

>    Currently, yes, it is the only approach.
>    Hope the above helps,

So the balance finished, and metadata is still almost full:

# btrfs fi df /home
Data, RAID1: total=1.60TiB, used=1.58TiB
System, RAID1: total=32.00MiB, used=248.00KiB
Metadata, RAID1: total=49.00GiB, used=47.24GiB

Confused about the output - does it actually look any better?


# btrfs fi show /home
Label: crawler-btrfs  uuid: 60f1759c-45f6-4484-9f60-66a4e9bbf2b6
        Total devices 2 FS bytes used 1.63TiB
        devid    3 size 2.56TiB used 1.66TiB path /dev/sdb4
        devid    4 size 2.56TiB used 1.66TiB path /dev/sda4

Btrfs v3.12


Does it mean that data/system/metadata will be able to grow now,
until their size in total in 2.56TiB?

-- 
Tomasz Chmielewski
http://wpkg.org

  reply	other threads:[~2013-12-18 14:54 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
2013-12-18 14:54   ` Tomasz Chmielewski [this message]
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=20131218235439.480170e0@virtall.com \
    --to=tch@virtall.com \
    --cc=hugo@carfax.org.uk \
    --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.