From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: speed up cp --reflink=always
Date: Sun, 16 Oct 2016 00:37:21 +0200 [thread overview]
Message-ID: <4e88008a-b844-e7d6-cba3-f86ce976b753@mendix.com> (raw)
In-Reply-To: <6e902770-05f3-2562-eeb3-dd9ef53b9406@profihost.ag>
Hi,
On 10/15/2016 10:49 PM, Stefan Priebe - Profihost AG wrote:
>
> cp --reflink=always takes sometimes very long. (i.e. 25-35 minutes)
>
> An example:
>
> source file:
> # ls -la vm-279-disk-1.img
> -rw-r--r-- 1 root root 204010946560 Oct 14 12:15 vm-279-disk-1.img
>
> target file after around 10 minutes:
> # ls -la vm-279-disk-1.img.tmp
> -rw-r--r-- 1 root root 65022328832 Oct 15 22:13 vm-279-disk-1.img.tmp
Two quick thoughts:
1. How many extents does this img have?
2. Is this an XY problem? Why not just put the img in a subvolume and
snapshot that?
K
next prev parent reply other threads:[~2016-10-15 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 20:49 speed up cp --reflink=always Stefan Priebe - Profihost AG
2016-10-15 22:37 ` Hans van Kranenburg [this message]
2016-10-16 18:54 ` Stefan Priebe - Profihost AG
2016-10-16 19:48 ` Hans van Kranenburg
2016-10-16 19:57 ` Stefan Priebe - Profihost AG
2016-10-16 20:00 ` Hans van Kranenburg
2016-10-17 1:50 ` Qu Wenruo
2016-10-17 6:50 ` Stefan Priebe - Profihost AG
2016-10-18 4:27 ` Duncan
2016-10-18 6:57 ` Qu Wenruo
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=4e88008a-b844-e7d6-cba3-f86ce976b753@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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