From: "J. Hart" <jfhart085@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: quwenruo@cn.fujitsu.com, o.freyermuth@googlemail.com
Subject: Re: btrfs send extremely slow (almost stuck)
Date: Fri, 14 Apr 2017 11:33:37 -0400 [thread overview]
Message-ID: <58F0EBD1.70905@gmail.com> (raw)
on 30.08.2016 at 02:48 Qu Wenruo wrote :
> Not the first, but although still few.
> There is a xfstest case submitted for it, and even before the test
case, there are already report from IRC.
> Anyway, I'll add Cc for you after the new IRC patch is out.
Please count me in.
I have this occur when I'm backing up a file server I use to hold
reflinked incrementals from client machines. Backing up from clients to
server is very quick (mere seconds, no incrementals there), but backup
of the server volume itself is very slow even with limited changes.
With clone detection enabled, that backup takes nearly seven hours.
Sending a complete volume to a blank filesystem (so no reflinks are
present at the destination) is a matter of only a few minutes.
Many thanks to Hermann Schwarzler whose suggestion led me onto this.
J. Hart
next reply other threads:[~2017-04-14 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-14 15:33 J. Hart [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-28 16:15 btrfs send extremely slow (almost stuck) Oliver Freyermuth
2016-08-28 21:41 ` james harvey
2016-08-29 17:50 ` Kai Krakow
2016-08-28 3:38 Oliver Freyermuth
2016-08-28 7:53 ` Duncan
2016-08-29 2:11 ` Qu Wenruo
2016-08-29 2:12 ` Qu Wenruo
2016-08-31 1:35 ` Jeff Mahoney
2016-08-31 1:54 ` Qu Wenruo
2016-08-29 10:02 ` Oliver Freyermuth
2016-08-30 0:48 ` Qu Wenruo
2016-09-04 21:41 ` Oliver Freyermuth
2016-09-05 5:21 ` Qu Wenruo
2016-09-05 21:29 ` Oliver Freyermuth
2016-09-06 2:13 ` Duncan
2016-09-06 22:24 ` Oliver Freyermuth
2016-09-06 2:46 ` Qu Wenruo
2016-09-06 21:53 ` Oliver Freyermuth
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=58F0EBD1.70905@gmail.com \
--to=jfhart085@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=o.freyermuth@googlemail.com \
--cc=quwenruo@cn.fujitsu.com \
/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).