All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: 5.13.8, enospc with 6G unused
Date: Mon, 30 Aug 2021 14:40:27 -0600	[thread overview]
Message-ID: <CAJCQCtSC4mx6cNf3mGDOEeWhJaTXK8s+WNWRTRDMt99k8O3LPw@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQPvw23CGvR307L-VyPSpZi3ovC3N+xp7OaMNrxSWir_w@mail.gmail.com>

Following the add device, filtered balance, remove device dance:

Overall:
    Device size:                  27.52GiB
    Device allocated:             21.52GiB
    Device unallocated:            6.00GiB
    Device missing:                  0.00B
    Used:                         21.15GiB
    Free (estimated):              6.30GiB      (min: 6.30GiB)
    Free (statfs, df):             6.30GiB
    Data ratio:                       1.00
    Metadata ratio:                   1.00
    Global reserve:               55.50MiB      (used: 0.00B)
    Multiple profiles:                  no

Data,single: Size:21.01GiB, Used:20.70GiB (98.56%)
   /dev/mapper/luks-4ac739d9-8d73-4913-89ac-656c79f89835          21.01GiB

Metadata,single: Size:520.00MiB, Used:456.52MiB (87.79%)
   /dev/mapper/luks-4ac739d9-8d73-4913-89ac-656c79f89835         520.00MiB

System,single: Size:4.00MiB, Used:16.00KiB (0.39%)
   /dev/mapper/luks-4ac739d9-8d73-4913-89ac-656c79f89835           4.00MiB

Unallocated:
   /dev/mapper/luks-4ac739d9-8d73-4913-89ac-656c79f89835           6.00GiB


So it's back to functional again but does seem like some kind of bug
that it had not allocated another metadata block group sooner when it
could have. Once all the space was locked up as data bg's, it was
inevitably going to get stuck like this.


Chris Murphy

  reply	other threads:[~2021-08-30 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 17:57 5.13.8, enospc with 6G unused Chris Murphy
2021-08-30 19:49 ` Chris Murphy
2021-08-30 19:52   ` Chris Murphy
2021-08-30 20:40     ` Chris Murphy [this message]
2021-08-31 12:36       ` David Sterba

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=CAJCQCtSC4mx6cNf3mGDOEeWhJaTXK8s+WNWRTRDMt99k8O3LPw@mail.gmail.com \
    --to=lists@colorremedies.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.