From: Roman Mamedov <rm@romanrm.net>
To: "Kline, Matthew" <matthew.kline@flukenetworks.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs balance fails with no space errors (despite having plenty)
Date: Wed, 25 Mar 2015 04:03:21 +0500 [thread overview]
Message-ID: <20150325040321.361abf2f@natsu> (raw)
In-Reply-To: <E8C63C11EA3FB04DBDFEDECEFD927FD1140C1E31@US-EVT-EXM04-P.global.tektronix.net>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
On Tue, 24 Mar 2015 22:25:30 +0000
"Kline, Matthew" <matthew.kline@flukenetworks.com> wrote:
> Sorry to necrobump this, but the issue came up again.
> I'm now on Linux 3.19.2 with btrfs-progs 3.19, and I converted my work laptop
> from ext4 to btrfs. Same issue - the conversion goes well,
> removing the ext* subvolume is fine, defragging is works,
> and then when I balance, it claims there is no space left on the device
> when the drive is 35% full. Dmesg is useless once again,
> giving only "1 enospc errors during balance".
>
> The last time this was an issue (the original post in this thread),
> I ended up just copying everything to an external drive,
> reformatting the btrfs partition, and copying things back.
>
> This time I did what was suggested below (moving all +1GB files off-drive
> to tmpfs and then back on) in case defrag missed something, and balance
> still fails. I was sure to rename the files and sync as suggested.
>
> Is there a known bug still lurking in ext4 conversion?
Post your "btrfs fi df" for the filesystem.
In my experience it looks like the conversion may designate large
portions of data as "metadata" for whatever reason.
A way to clean this up is to run
btrfs fi balance start -musage=5 -dusage=5 /path
try repeating this again and again increasing the value gradually from 5 to
50-70 in steps of 5 or 10.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-03-24 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 22:25 btrfs balance fails with no space errors (despite having plenty) Kline, Matthew
2015-03-24 23:03 ` Roman Mamedov [this message]
2015-03-24 23:09 ` Kline, Matthew
2015-03-24 23:14 ` Hugo Mills
2015-03-24 23:45 ` Kline, Matthew
2015-03-25 3:39 ` Russell Coker
2015-03-24 23:31 ` Roman Mamedov
-- strict thread matches above, loose matches on Subject: below --
2014-11-12 18:48 Kline, Matthew
2014-11-13 0:06 ` Oon-Ee Ng
2014-11-13 7:36 ` Duncan
2014-11-13 10:38 ` Hugo Mills
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=20150325040321.361abf2f@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=matthew.kline@flukenetworks.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).