Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: Can moving data to a subvolume not take as long as a fully copy?
Date: Mon, 14 Jan 2013 09:32:50 -0800	[thread overview]
Message-ID: <20130114173250.GA23026@merlins.org> (raw)

I made a mistake and copied data in the root of a new btrfs filesystem.
I created a subvolume, and used mv to put everything in there.
Something like:
cd /mnt
btrfs subvolume create dir
mv * dir

Except it's been running for over a day now (ok, it's 5TB of data)

Looks like mv is really copying all the data as if it were an entirely
different filesystem.

Is there not a way to short circuit this and only update the metadata?

Thanks,
Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  

             reply	other threads:[~2013-01-14 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 17:32 Marc MERLIN [this message]
2013-01-14 17:41 ` Can moving data to a subvolume not take as long as a fully copy? Hugo Mills
2013-01-14 18:00   ` Marc MERLIN
2013-01-14 18:13     ` Hugo Mills
2013-01-15  6:48 ` David Brown
2013-01-15 14:49   ` Marc MERLIN
2013-01-15 17:45     ` Mitch Harder

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=20130114173250.GA23026@merlins.org \
    --to=marc@merlins.org \
    --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