All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hubert Kario <hka@qbs.com.pl>
To: helmut@hullen.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs balance
Date: Thu, 20 Jan 2011 18:46:20 +0100	[thread overview]
Message-ID: <201101201846.20370.hka@qbs.com.pl> (raw)
In-Reply-To: <BeD$lESD1uB@helmut.hullen.de>

On Thursday, January 20, 2011 14:40:00 Helmut Hullen wrote:
> Hallo, Andreas,
>=20
> 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, whe=
n
> > it is (really) worth doing a balance?
>=20
> 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).
>=20
That's the effect of lots of IO. IMHO it shouldn't take more than 4-8h =
for 1TB=20
7200rpm disks in an otherwise idle system, as such it's rather ineffici=
ent=20
right now.

--=20
Hubert Kario
QBS - Quality Business Software
02-656 Warszawa, ul. Ksawer=F3w 30/85
tel. +48 (22) 646-61-51, 646-74-24
www.qbs.com.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-01-20 17:46 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
2011-01-20 17:46   ` Hubert Kario [this message]
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=201101201846.20370.hka@qbs.com.pl \
    --to=hka@qbs.com.pl \
    --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 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.