From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: Marc Haber <mh+linux-btrfs@zugschlus.de>, linux-btrfs@vger.kernel.org
Subject: Re: balance hangs and starts again on reboot
Date: Sat, 5 Mar 2016 19:00:29 +0100 [thread overview]
Message-ID: <56DB1EBD.2070904@googlemail.com> (raw)
In-Reply-To: <20160305172553.GF1902@torres.zugschlus.de>
On 03/05/16 18:25, Marc Haber wrote:
> On Sat, Mar 05, 2016 at 04:38:57PM +0100, Holger Hoffstätte wrote:
>> On 03/05/16 15:17, Marc Haber wrote:
>>>> Then try to balance in small increments.
>>>
>>> -dusage=5 and incrementing? Or what do you mean with "in small
>>> increments"?
>>
>> Exactly, yes. Sorry for not being more clear.
>
> So you would recommend something along
>
> for nr in $(seq 5 5 100); do
> btrfs balance start -dusage=$nr $FS
> done
>
> right?
Except for the 100 part, which seems pointless. Maybe more like
10,20..80 max. If that doesn't help you are probably out of space
anyway.
> Won't this take ages longer than a straight unfiltered balance?
Touching less stuff conditionally is pretty much guaranteed to be
faster than unconditionally rewriting everything, and less likely to
end up out of space since you garbage-collect the smallest chunks
first, freeing up a larger one and so on.
> md as in the Linux Software RAID? That's not in the game here, it's a
> single SATA hard disk.
I thought your df output contained md or something. If not, all the
better.
-h
next prev parent reply other threads:[~2016-03-05 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 17:31 balance hangs and starts again on reboot Marc Haber
2016-03-04 18:09 ` Holger Hoffstätte
2016-03-05 14:17 ` Marc Haber
2016-03-05 15:38 ` Holger Hoffstätte
2016-03-05 17:25 ` Marc Haber
2016-03-05 18:00 ` Holger Hoffstätte [this message]
2016-03-06 6:12 ` Duncan
2016-03-04 19:08 ` Chris Murphy
2016-03-05 14:12 ` Marc Haber
2016-03-05 17:07 ` 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=56DB1EBD.2070904@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mh+linux-btrfs@zugschlus.de \
/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.