From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Bob Williams <linux@barrowhillfarm.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: A question about subvolumes
Date: Sat, 05 Jul 2014 12:06:18 -0400 [thread overview]
Message-ID: <53B8227A.30809@gmail.com> (raw)
In-Reply-To: <53B7E4D1.9070803@barrowhillfarm.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
On 07/05/2014 07:43 AM, Bob Williams wrote:
> 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
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I'm pretty certain that recent versions of the GNU Coreutils will
automatically try a reflink for cp if the underlying filesystem is
BTRFS. I'm not 100% certain about this as I've just aliases cp to 'cp
--reflink=auto' on all my systems.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2014-07-05 16:06 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
2014-07-05 16:06 ` Austin S Hemmelgarn [this message]
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=53B8227A.30809@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux@barrowhillfarm.org.uk \
/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.