From: Bob Williams <linux@barrowhillfarm.org.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: A question about subvolumes
Date: Sat, 05 Jul 2014 12:43:13 +0100 [thread overview]
Message-ID: <53B7E4D1.9070803@barrowhillfarm.org.uk> (raw)
In-Reply-To: <53B79AE4.3030404@libero.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/07/14 07:27, Goffredo Baroncelli wrote:
> On 07/04/2014 11:06 PM, Bob Williams wrote:
>> On 04/07/14 21:38, Goffredo Baroncelli wrote:
>
>>
>> Thank you, Goffredo. As the current /home/bob is not a
>> subvolume, but a regular linux directory/folder, will the "cp
>> --reflink" still carry the same speed advantage?
>>
>> In other words, using your example above, will this work:
>>
>> # cp --reflink -R normal_directory-A/* subvolume-B/ # rm -rf
>> normal_directory-A/
>
> Yes.
>
> If you want to move (or copy) files between subvolume, cp
> --reflink is faster.
>
>
> I have to point out that the "--reflink" is only an internal
> detail. The two file are logically separated: if you after the
> copy change the source, the destination is unaffected.
>
Many thanks. Conversion of /home/bob to a subvolume completed
uneventfully. :-) And very quickly, considering it is ~500GB. I have
made a note of that --reflink option.
Bob
- --
Bob Williams
System: Linux 3.11.10-17-desktop
Distro: openSUSE 13.1 (x86_64) with KDE Development Platform: 4.13.2
Uptime: 06:00am up 6 days 20:14, 4 users, load average: 0.02, 0.18, 0.25
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlO35NAACgkQ0Sr7eZJrmU6YWgCgiriAUJF8Ee01ckev67fBTe6P
/WIAnjs2DnzqPU+nUFhCiyN4K212n893
=gSrD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-07-05 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 14:38 A question about subvolumes Bob Williams
2014-07-04 20:38 ` Goffredo Baroncelli
2014-07-04 21:06 ` Bob Williams
2014-07-05 6:27 ` Goffredo Baroncelli
2014-07-05 11:43 ` Bob Williams [this message]
2014-07-05 16:06 ` Austin S Hemmelgarn
2014-07-05 23:49 ` Chris Samuel
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=53B7E4D1.9070803@barrowhillfarm.org.uk \
--to=linux@barrowhillfarm.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 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.