From: Shriramana Sharma <samjnaa@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Shriramana Sharma <samjnaa@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Moving contents from one subvol to another
Date: Sat, 29 Nov 2014 20:45:34 +0530 [thread overview]
Message-ID: <CAH-HCWWh02invDCdx4-bPORdg4r39efsW=buKXTVtfspSQ9sVA@mail.gmail.com> (raw)
In-Reply-To: <20141129142813.GD32735@carfax.org.uk>
On Sat, Nov 29, 2014 at 7:58 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> The latest version of mv should be able to use CoW copies to make
> it more efficient. It has a --reflink option, the same as cp. Note
> that you can't make reflinks crossing a mount boundary, but you can do
> so crossing a subvolume boundary (as you're doing here).
Hi thanks for this. I suppose you are referring to the commit:
http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=b47231be6813e6cb5305266e391b4bb745f27f13
>From http://git.savannah.gnu.org/cgit/coreutils.git/log/?qt=grep&q=mv%3A,
http://git.savannah.gnu.org/cgit/coreutils.git/plain/NEWS?id=b47231be6813e6cb5305266e391b4bb745f27f13
and finally http://git.savannah.gnu.org/cgit/coreutils.git/tree/src/mv.c?id=b47231be6813e6cb5305266e391b4bb745f27f13
it doesn't seem as if there was any earlier commit actually adding a
--reflink option so it seems the improvement is in-built.
That's nice to know!
Any idea when the next coreutils point release with this will be out?
--
Shriramana Sharma ஶ்ரீரமணஶர்மா श्रीरमणशर्मा
next prev parent reply other threads:[~2014-11-29 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 14:21 Moving contents from one subvol to another Shriramana Sharma
2014-11-29 14:28 ` Hugo Mills
2014-11-29 15:15 ` Shriramana Sharma [this message]
2014-11-29 17:07 ` Robert White
2014-11-30 3:53 ` Shriramana Sharma
2014-11-30 13:04 ` Shriramana Sharma
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='CAH-HCWWh02invDCdx4-bPORdg4r39efsW=buKXTVtfspSQ9sVA@mail.gmail.com' \
--to=samjnaa@gmail.com \
--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).