From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: 3.16 Managed to ENOSPC with <80% used
Date: Thu, 25 Sep 2014 21:21:47 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.09.25.21.21.47@googlemail.com> (raw)
In-Reply-To: CAPL5yKdt7eTk-+0NP2Y9Aa8zNQqJpujTm31z_ee04OS3DocMXg@mail.gmail.com
On Thu, 25 Sep 2014 17:05:11 -0400, Dan Merillat wrote:
> Deleting files or dropping snapshots is difficult when it's wedged as
> well, a lot of disk activity (journal thrash?) and no persistent
> progress - a reboot brigs the deleted files back. I eventually
> managed to empty a single data chunk and after that it was a trivial
> recovery.
That's why I mentioned adding a second device - that will immediately
allow cleanup with headroom. An additional 8GB tmpfs volume can works
wonders.
>> That particular workload seems to cause the block allocator to go
>> on a spending spree; you're not the first to see this.
>
> I could see normal-user usage patterns getting ignored, but this is
> the patterns of the people working on BTRFS. Maybe they need to
> remove their balance cronjobs for a while. :)
Well..some remedy is coming:
https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git/commit/fs/btrfs?h=integration&id=47ab2a6c689913db23ccae38349714edf8365e0a
Not sure how many preliminaries that patch needs, but if you are
comfortable with patching/building your kernel you could give that
a try. I'm sure Josef would love some feedback.
Glad you're back on track. :)
Holger
next prev parent reply other threads:[~2014-09-25 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 20:43 3.16 Managed to ENOSPC with <80% used Dan Merillat
2014-09-24 22:23 ` Holger Hoffstätte
2014-09-25 21:05 ` Dan Merillat
2014-09-25 21:21 ` Holger Hoffstätte [this message]
2014-09-26 14:18 ` Rich Freeman
2014-09-27 2:36 ` Duncan
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.25.21.21.47@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.