linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Kapusta <roman.kapusta@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: performance of cp and mv between subvolumes
Date: Thu, 7 Oct 2010 11:57:02 +0200	[thread overview]
Message-ID: <AANLkTi=yk9zZuF-tTOgGj1Vt2=WHOOH5BYyzX+3sBdTZ@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikwYXktHD7-H7LF+cn7zBpY8ZdDw+z=Zze1-C+w@mail.gmail.com>

Shouldn't be possible to move or copy (COW) big files between two
subvolumes of one btrfs filesystem instantly - without real data
movement?

cp --reflink between subvolumes is returning error: cp: failed to
clone `...': Invalid cross-device link
mv between subvolumes is really slow - looks like it is moving all data

To circumvent this I can create new snapshot and then remove
everything except files I want to copy/move to this new subvolume and
I gained the same effect quite fast, but indirectly, is there some way
how to do it directly when subvolume already exists?

Roman Kapusta

           reply	other threads:[~2010-10-07  9:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <AANLkTikwYXktHD7-H7LF+cn7zBpY8ZdDw+z=Zze1-C+w@mail.gmail.com>]

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='AANLkTi=yk9zZuF-tTOgGj1Vt2=WHOOH5BYyzX+3sBdTZ@mail.gmail.com' \
    --to=roman.kapusta@gmail.com \
    --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).