From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>, chris@colorremedies.com
Subject: Re: how to understand "btrfs fi show" output? "No space left" issues
Date: Tue, 27 Sep 2016 12:10:37 +0900 [thread overview]
Message-ID: <8f88272e6c5e69563d6734f411c680ae@admin.virtall.com> (raw)
In-Reply-To: <CAJCQCtQ+uaMCCW81+ePF6scGsTu+MEu1arCQ0wTJhwS8EN8S=A@mail.gmail.com>
On 2016-09-21 11:51, Chris Murphy wrote:
> So if it happens again, first capture the above two bits of
> information, and then if you feel like testing kernel 4.8rc7 do that.
> It has a massive pile of enoscp related rework and I bet Josef would
> like to know if the problem reproduces with that kernel. As in, just
> change kernels, don't try to fix it with balance first.
Looks like 4.8 helped (running 4.8rc8 now).
With 4.7, after balance, the "used" value continued to grow, to around
300 GB, although used space shown by "df" was more or less constant at
130-140 GB:
# btrfs fi show /var/lib/lxd
Label: 'btrfs' uuid: f5f30428-ec5b-4497-82de-6e20065e6f61
Total devices 2 FS bytes used 135.40GiB <--------- was growing
devid 1 size 423.13GiB used 277.03GiB path /dev/sda3
devid 2 size 423.13GiB used 277.03GiB path /dev/sdb3
After upgrading to 4.8rc8, "used" value dropped, so hopefully it's fixed
now.
Tomasz Chmielewski
https://lxadm.com
next prev parent reply other threads:[~2016-09-27 3:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 6:47 how to understand "btrfs fi show" output? "No space left" issues Tomasz Chmielewski
2016-09-20 6:58 ` Hugo Mills
2016-09-20 7:26 ` Tomasz Chmielewski
2016-09-20 7:27 ` Peter Becker
2016-09-20 7:28 ` Peter Becker
2016-09-20 7:30 ` Peter Becker
2016-09-20 7:51 ` Tomasz Chmielewski
2016-09-20 7:56 ` Tomasz Chmielewski
2016-09-20 8:20 ` Peter Becker
2016-09-20 8:30 ` Andrei Borzenkov
2016-09-20 8:54 ` Peter Becker
2016-09-20 8:34 ` Peter Becker
2016-09-20 8:48 ` Hugo Mills
2016-09-20 8:59 ` Peter Becker
2016-09-20 9:10 ` Peter Becker
2016-11-14 15:37 ` Johannes Hirte
2016-09-21 2:51 ` Chris Murphy
2016-09-27 3:10 ` Tomasz Chmielewski [this message]
2016-11-13 13:47 ` Tomasz Chmielewski
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=8f88272e6c5e69563d6734f411c680ae@admin.virtall.com \
--to=mangoo@wpkg.org \
--cc=chris@colorremedies.com \
--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).