From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Shrinking a device - performance?
Date: Fri, 31 Mar 2017 05:38:36 +0000 (UTC) [thread overview]
Message-ID: <pan$76dc7$170a959f$9df83808$fddf3918@cox.net> (raw)
In-Reply-To: pan$5c23$ddaeadec$128532fd$8595ddc4@cox.net
Duncan posted on Fri, 31 Mar 2017 05:26:39 +0000 as excerpted:
> Compare that to the current thread where someone's trying to do a resize
> of a 20+ TB btrfs and it was looking to take a week, due to the massive
> size and the slow speed of balance on his highly reflinked filesystem on
> spinning rust.
Heh, /this/ thread. =:^) I obviously lost track of the thread I was
replying to.
Which in a way makes the reply even more forceful, as it's obviously
generically targeted, not just at this thread. Even if I were so devious
as to arrange that deliberately (I'm not and I didn't, FWIW, but of
course if you suspect that than this assurance won't mean much either).
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-03-31 5:38 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
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 [this message]
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='pan$76dc7$170a959f$9df83808$fddf3918@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).