From: Cloud Admin <admin@cloud.haefemeier.eu>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Best Practice: Add new device to RAID1 pool
Date: Tue, 25 Jul 2017 19:56:22 +0200 [thread overview]
Message-ID: <1501005382.3020.4.camel@cloud.haefemeier.eu> (raw)
In-Reply-To: <20170724204257.GJ7140@carfax.org.uk>
Am Montag, den 24.07.2017, 20:42 +0000 schrieb Hugo Mills:
> On Mon, Jul 24, 2017 at 02:35:05PM -0600, Chris Murphy wrote:
> > On Mon, Jul 24, 2017 at 5:27 AM, Cloud Admin <admin@cloud.haefemeie
> > r.eu> wrote:
> >
> > > I am a little bit confused because the balance command is running
> > > since
> > > 12 hours and only 3GB of data are touched.
> >
> > That's incredibly slow. Something isn't right.
> >
> > Using btrfs-debug -b from btrfs-progs, I've selected a few 100%
> > full chunks.
> >
> > [156777.077378] f26s.localdomain sudo[13757]: chris : TTY=pts/2
> > ;
> > PWD=/home/chris ; USER=root ; COMMAND=/sbin/btrfs balance start
> > -dvrange=157970071552..159043813376 /
> > [156773.328606] f26s.localdomain kernel: BTRFS info (device sda1):
> > relocating block group 157970071552 flags data
> > [156800.408918] f26s.localdomain kernel: BTRFS info (device sda1):
> > found 38952 extents
> > [156861.343067] f26s.localdomain kernel: BTRFS info (device sda1):
> > found 38951 extents
> >
> > That 1GiB chunk with quite a few fragments took 88s. That's 11MB/s.
> > Even for a hard drive, that's slow. I've got maybe a dozen
> > snapshots
> > on this particular volume and quotas are not enabled. By definition
> > all of those extents are sequential. So I'm not sure why it's
> > taking
> > so long. Seems almost like a regression somewhere. A nearby chunk
> > with
> > ~23k extents only takes 45s to balance. And another chunk with
> > ~32000
> > extents took 55s to balance.
>
> In my experience, it's pretty consistent at about a minute per 1
> GiB for data on rotational drives on RAID-1. For metadata, it can go
> up to several hours (or more) per 256 MiB chunk, depending on what
> kind of metadata it is. With extents shared between lots of files, it
> slows down. In my case, with a few hundred snapshots of the same
> thing, my system was taking 4h per chunk for the chunks full of the
> extent tree.
After disabling quota the balancing is no working faster. After 27h
approx. 1.3TB are done. It has taken around 4h of rearrange the data on
the old three discs the process started to use the new one. Since there
it is processing much faster.
Bye
Frank
next prev parent reply other threads:[~2017-07-25 17:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 11:27 Best Practice: Add new device to RAID1 pool Cloud Admin
2017-07-24 13:46 ` Austin S. Hemmelgarn
2017-07-24 14:08 ` Roman Mamedov
2017-07-24 16:42 ` Cloud Admin
2017-07-24 14:12 ` Cloud Admin
2017-07-24 14:25 ` Austin S. Hemmelgarn
2017-07-24 16:40 ` Cloud Admin
2017-07-29 23:04 ` Best Practice: Add new device to RAID1 pool (Summary) Cloud Admin
2017-07-31 11:52 ` Austin S. Hemmelgarn
2017-07-24 20:35 ` Best Practice: Add new device to RAID1 pool Chris Murphy
2017-07-24 20:42 ` Hugo Mills
2017-07-24 20:55 ` Chris Murphy
2017-07-24 21:00 ` Hugo Mills
2017-07-24 21:17 ` Adam Borowski
2017-07-24 23:18 ` Chris Murphy
2017-07-25 17:56 ` Cloud Admin [this message]
2017-07-24 21:12 ` waxhead
2017-07-24 21:20 ` Chris Murphy
2017-07-25 2:22 ` Marat Khalili
2017-07-25 8:13 ` Chris Murphy
2017-07-25 17:46 ` Cloud Admin
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=1501005382.3020.4.camel@cloud.haefemeier.eu \
--to=admin@cloud.haefemeier.eu \
--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).