linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephane Chazelas <stephane.chazelas@googlemail.com>
To: helmut@hullen.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs balancing start - and stop?
Date: Fri, 01 Apr 2011 19:33:30 +0100	[thread overview]
Message-ID: <1301682810.11424.5.camel@sc.lan> (raw)
In-Reply-To: <Bj0igski1uB@helmut.hullen.de>

On Fri, 2011-04-01 at 14:12 +0200, Helmut Hullen wrote:
> Hallo, Struan,
> 
> Du meintest am 01.04.11:
> 
> > 1) Is the balancing operation expected to take many hours (or days?)
> > on a filesystem such as this? Or are there known issues with the
> > algorithm that are yet to be addressed?
> 
> May be. Balancing about 15 GByte needed about 2 hours (or less),  
> balancing about 2 TByte needed about 20 hours.
[...]

I've got a balance running since Monday on a 9TB volume (3.5 of which
are used, 3.2 allegedly free), showing no sign of finishing soon. Should
I be worried?

Using /proc/sys/vm/block_dump, I can see it's seeking all over the
place, which is probably why throughput is not high. I can also see it
writing several times to the same sectors.

# df -h /backup
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda4             8.2T  3.5T  3.2T  53% /backup
# btrfs fi sh
Label: none  uuid: ...
        Total devices 3 FS bytes used 3.43TB
        devid    4 size 2.73TB used 1.16TB path /dev/sdc
        devid    3 size 2.73TB used 1.16TB path /dev/sdb
        devid    2 size 2.70TB used 1.14TB path /dev/sda4

Btrfs Btrfs v0.19
# ps -eolstart,args | grep balance
Mon Mar 28 11:18:18 2011 sudo btrfs fi balance /backup
Mon Mar 28 11:18:18 2011 btrfs fi balance /backup
# date
Fri Apr  1 19:28:40 BST 2011
# btrfs fi df /backup
Data, RAID0: total=3.41TB, used=3.41TB
System, RAID1: total=16.00MB, used=232.00KB
Metadata, RAID1: total=27.75GB, used=20.47GB
# iostat -md
Device:            tps    MB_read/s    MB_wrtn/s    MB_read    MB_wrtn
sda              14.49         2.37         2.39     903123     913112
sdc             501.23         2.68         5.06    1022456    1928462
sdb             477.28         2.58         5.06     982853    1928482

It's already written more than the used space.

Cheers,
Stephane


  parent reply	other threads:[~2011-04-01 18:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-01 11:14 btrfs balancing start - and stop? Struan Bartlett
2011-04-01 11:59 ` Hugo Mills
2011-04-05 16:06   ` Struan Bartlett
2011-04-01 12:12 ` Helmut Hullen
2011-04-01 13:22   ` Konstantinos Skarlatos
2011-04-01 13:36     ` Helmut Hullen
2011-04-01 13:52       ` Hugo Mills
     [not found]     ` <20110401133736.GB2984@carfax.org.uk>
2011-04-01 14:24       ` Konstantinos Skarlatos
2011-04-01 18:33   ` Stephane Chazelas [this message]
2011-04-01 19:26     ` Helmut Hullen
2011-04-03 18:53       ` Stephane Chazelas
2011-04-03 19:35         ` Helmut Hullen
2011-04-04 19:07           ` Stephane Chazelas
2011-04-06 11:43             ` Stephane Chazelas
2011-04-11  8:42               ` Stephane Chazelas
2011-04-11  9:14                 ` Helmut Hullen

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=1301682810.11424.5.camel@sc.lan \
    --to=stephane.chazelas@googlemail.com \
    --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).