Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Bob Williams <linux@barrowhillfarm.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: A question about subvolumes
Date: Sat, 05 Jul 2014 08:27:48 +0200	[thread overview]
Message-ID: <53B79AE4.3030404@libero.it> (raw)
In-Reply-To: <53B7176F.1020409@barrowhillfarm.org.uk>

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.

> 
> 
> --
> 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
> 

-- 
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  reply	other threads:[~2014-07-05  6:23 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 [this message]
2014-07-05 11:43       ` Bob Williams
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=53B79AE4.3030404@libero.it \
    --to=kreijack@libero.it \
    --cc=kreijack@inwind.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox