From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs balance
Date: 20 Jan 2011 14:40:00 +0100 [thread overview]
Message-ID: <BeD$lESD1uB@helmut.hullen.de> (raw)
In-Reply-To: <4D38338B.3090903@gmail.com>
Hallo, Andreas,
Du meintest am 20.01.11:
> Maybe it is a very stupid question but I want to ask it anyway. In
> general, 'btrfs filesystem balance' takes very long to finish and
> produces lots of IO. So what are the classical usage scenarios, when
> it is (really) worth doing a balance?
Here (Kernel 2.6.37, btrfs git Nov. 2010): balancing two disks/
partitions with 2 and 1.5 TByte needs about 24 hours (CPU 1.5 GHz).
What do you mean with "lots of IO"? the messages in "/var/log/messages"
and "/var/log/warn"?
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2011-01-20 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 13:07 Btrfs balance Andreas Philipp
2011-01-20 13:39 ` Hugo Mills
[not found] ` <4D384C75.5090202@gmail.com>
2011-01-20 15:09 ` Hugo Mills
2011-01-20 13:40 ` Helmut Hullen [this message]
2011-01-20 17:46 ` Hubert Kario
2011-01-20 21:31 ` Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2011-01-20 14:58 Tomasz Chmielewski
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='BeD$lESD1uB@helmut.hullen.de' \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--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 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).