From: Calvin Walton <calvin.walton@kepstin.ca>
To: Brendan Hide <brendan@swiftspirit.co.za>
Cc: Marc MERLIN <marc@merlins.org>, linux-btrfs@vger.kernel.org
Subject: Re: Please review and comment, dealing with btrfs full issues
Date: Mon, 05 May 2014 14:36:09 -0400 [thread overview]
Message-ID: <1399314969.4155.1.camel@sasami> (raw)
In-Reply-To: <5367C551.6020604@swiftspirit.co.za>
On Mon, 2014-05-05 at 19:07 +0200, Brendan Hide wrote:
> On 05/05/14 14:16, Marc MERLIN wrote:
> > I've just written this new page:
> > http://marc.merlins.org/perso/btrfs/post_2014-05-04_Fixing-Btrfs-Filesystem-Full-Problems.html
> >
> > First, are there problems in it?
> >
> > Second, are there other FS full issues I should mention in it?
> >
> The issue I'm not sure of how to get through is if you can't balance
> *because* of ENOSPC errors. I'd probably start scouring the mailing list
> archives if I ever come across that.
The standard response on the mailing list for this issue is to
temporarily add an additional device to the filesystem (even e.g. a 4GB
USB flash drive is often enough) - this will add space to allocate a few
new chunks, allowing the balance to proceed. You can remove the extra
device after the balance completes.
--
Calvin Walton <calvin.walton@kepstin.ca>
next prev parent reply other threads:[~2014-05-05 18:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 12:16 Please review and comment, dealing with btrfs full issues Marc MERLIN
2014-05-05 17:07 ` Brendan Hide
2014-05-05 17:09 ` Brendan Hide
2014-05-05 18:36 ` Calvin Walton [this message]
2014-05-06 4:41 ` Russell Coker
2014-05-06 12:19 ` Marc MERLIN
2014-05-06 16:30 ` Brendan Hide
2014-05-06 16:43 ` Hugo Mills
2014-05-07 14:09 ` David Sterba
2014-05-07 14:23 ` Smallest-n balance filter (was Re: Please review and comment, dealing with btrfs full issues) Hugo Mills
2014-05-07 14:50 ` David Sterba
2014-05-06 21:20 ` Please review and comment, dealing with btrfs full issues Duncan
2014-05-06 21:43 ` 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=1399314969.4155.1.camel@sasami \
--to=calvin.walton@kepstin.ca \
--cc=brendan@swiftspirit.co.za \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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.