From: Christian Theune <ct@flyingcircus.io>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Shrinking a device - performance?
Date: Mon, 27 Mar 2017 15:20:37 +0200 [thread overview]
Message-ID: <3558CE2F-0B8F-437B-966C-11C1392B81F2@flyingcircus.io> (raw)
In-Reply-To: <20170327130730.GN11714@carfax.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]
Hi,
> On Mar 27, 2017, at 3:07 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
>
> On my hardware (consumer HDDs and SATA, RAID-1 over 6 devices), it
> takes about a minute to move 1 GiB of data. At that rate, it would
> take 1000 minutes (or about 16 hours) to move 1 TiB of data.
>
> However, there are cases where some items of data can take *much*
> longer to move. The biggest of these is when you have lots of
> snapshots. When that happens, some (but not all) of the metadata can
> take a very long time. In my case, with a couple of hundred snapshots,
> some metadata chunks take 4+ hours to move.
Thanks for that info. The 1min per 1GiB is what I saw too - the “it can take longer” wasn’t really explainable to me.
As I’m not using snapshots: would large files (100+gb) with long chains of CoW history (specifically reflink copies) also hurt?
Something I’d like to verify: does having traffic on the volume have the potential to delay this infinitely? I.e. does the system write to any segments that we’re trying to free so it may have to work on the same chunk over and over again? If not, then this means it’s just slow and we’re looking forward to about 2 months worth of time shrinking this volume. (And then again on the next bigger server probably about 3-4 months).
(Background info: we’re migrating large volumes from btrfs to xfs and can only do this step by step: copying some data, shrinking the btrfs volume, extending the xfs volume, rinse repeat. If someone should have any suggestions to speed this up and not having to think in terms of _months_ then I’m all ears.)
Cheers,
Christian
--
Christian Theune · ct@flyingcircus.io · +49 345 219401 0
Flying Circus Internet Operations GmbH · http://flyingcircus.io
Forsterstraße 29 · 06112 Halle (Saale) · Deutschland
HR Stendal HRB 21169 · Geschäftsführer: Christian. Theune, Christian. Zagrodnick
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 496 bytes --]
next prev parent reply other threads:[~2017-03-27 13:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 11:17 Shrinking a device - performance? Christian Theune
2017-03-27 13:07 ` Hugo Mills
2017-03-27 13:20 ` Christian Theune [this message]
2017-03-27 13:24 ` Hugo Mills
2017-03-27 13:46 ` Austin S. Hemmelgarn
2017-03-27 13:50 ` Christian Theune
2017-03-27 13:54 ` Christian Theune
2017-03-27 14:17 ` Austin S. Hemmelgarn
2017-03-27 14:49 ` Christian Theune
2017-03-27 15:06 ` Roman Mamedov
2017-04-01 9:05 ` Kai Krakow
2017-03-27 14:14 ` Austin S. Hemmelgarn
2017-03-27 14:48 ` Roman Mamedov
2017-03-27 14:53 ` Christian Theune
2017-03-28 14:43 ` Peter Grandi
2017-03-28 14:50 ` Tomasz Kusmierz
2017-03-28 15:06 ` Peter Grandi
2017-03-28 15:35 ` Tomasz Kusmierz
2017-03-28 16:20 ` Peter Grandi
2017-03-28 14:59 ` Peter Grandi
2017-03-28 15:20 ` Peter Grandi
2017-03-28 15:56 ` Austin S. Hemmelgarn
2017-03-30 15:55 ` Peter Grandi
2017-03-31 12:41 ` Austin S. Hemmelgarn
2017-03-31 17:25 ` Peter Grandi
2017-03-31 19:38 ` GWB
2017-03-31 20:27 ` Peter Grandi
2017-04-01 0:02 ` GWB
2017-04-01 2:42 ` Duncan
2017-04-01 4:26 ` GWB
2017-04-01 11:30 ` Peter Grandi
2017-03-30 15:00 ` Piotr Pawłow
2017-03-30 16:13 ` Peter Grandi
2017-03-30 22:13 ` Piotr Pawłow
2017-03-31 1:00 ` GWB
2017-03-31 5:26 ` Duncan
2017-03-31 5:38 ` Duncan
2017-03-31 12:37 ` Peter Grandi
2017-03-31 11:37 ` Peter Grandi
2017-03-31 10:51 ` Peter Grandi
-- strict thread matches above, loose matches on Subject: below --
2017-03-27 11:51 Christian Theune
2017-03-27 12:55 ` Christian Theune
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=3558CE2F-0B8F-437B-966C-11C1392B81F2@flyingcircus.io \
--to=ct@flyingcircus.io \
--cc=hugo@carfax.org.uk \
--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).