From: Matthieu Dalstein <matthieu.dalstein@dalmat.net>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Ability to free space on a full btrfs filesystem
Date: Mon, 26 Aug 2013 23:43:22 +0200 [thread overview]
Message-ID: <521BCBFA.8040506@dalmat.net> (raw)
In-Reply-To: <502292E7-02F9-4398-905B-BA58D186CA7E@colorremedies.com>
> I don't know if removing a snapshot will necessarily help but it may be worth a try and see if these numbers change enough to allow file deletion.
Actually the snapshots could not be removed due to the unsufficient
remaining space.
> Another way out of this that's worked for some people in the past is to btrfs device add another disk to the volume. Maybe just 1GB of USB stick space is enough so that it can allocate another metadata chunk. But I'd give it as much of the fastest storage you have: can be any disk partition, or LV. But I've also done it with a USB stick partition.
>
> After it's added, see if you can do a balance, which should free most of those 141GB of data chunks. And then you can btrfs device delete the recently added device, which will move whatever data/metadata chunks are on it, back to the primary device for the volume.
Thanks for the tip. I would have expected another less intrusive
recovery but this one worked well. I did not fully rebalance the fs
(could have lasted days!) but with the d/m usage balance parameters I
managed to get back to a good state.
I guess this means I should find ways to avoid full fs unless there is a
plan to recover gracefully from such situations.
Thanks
--
Matthieu
next prev parent reply other threads:[~2013-08-26 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-25 16:23 Ability to free space on a full btrfs filesystem Matthieu Dalstein
2013-08-25 16:29 ` Marc MERLIN
2013-08-25 19:29 ` Chris Murphy
2013-08-26 21:43 ` Matthieu Dalstein [this message]
2013-08-27 0:16 ` Chris Murphy
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=521BCBFA.8040506@dalmat.net \
--to=matthieu.dalstein@dalmat.net \
--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.