From: Marc Joliet <marcec@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: Move data and mount point to subvolume
Date: Tue, 18 Sep 2018 20:10:23 +0200 [thread overview]
Message-ID: <2062209.NsJ275U7B3@thetick> (raw)
In-Reply-To: <7fade1e9-7eb2-d416-6a3d-452cbca3bbe5@mendix.com>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Am Sonntag, 16. September 2018, 14:50:04 CEST schrieb Hans van Kranenburg:
> The last example, where you make a subvolume and move everything into
> it, will not do what you want. Since a subvolume is a separate new
> directoty/file hierarchy, mv will turn into a cp and rm operation
> (without warning you) probably destroying information about data shared
> between files.
I thought that wasn't true anymore. The NEWS file to coreutils contains this
(for version 8.24):
mv will try a reflink before falling back to a standard copy, which is
more efficient when moving files across BTRFS subvolume boundaries.
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-18 23:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-16 11:14 Move data and mount point to subvolume Rory Campbell-Lange
2018-09-16 12:37 ` Hans van Kranenburg
2018-09-16 12:50 ` Hans van Kranenburg
2018-09-16 18:03 ` Rory Campbell-Lange
2018-09-16 18:13 ` Chris Murphy
2018-09-16 18:40 ` Rory Campbell-Lange
2018-09-16 19:44 ` Chris Murphy
2018-09-16 20:34 ` Rory Campbell-Lange
2018-09-18 18:10 ` Marc Joliet [this message]
2018-09-18 18:33 ` Hans van Kranenburg
2018-09-16 17:23 ` Rory Campbell-Lange
2018-09-16 18:04 ` Chris Murphy
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=2062209.NsJ275U7B3@thetick \
--to=marcec@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.