From: Bob Williams <linux@barrowhillfarm.org.uk>
To: linux-btrfs@vger.kernel.org
Subject: A question about subvolumes
Date: Fri, 04 Jul 2014 15:38:29 +0100 [thread overview]
Message-ID: <53B6BC65.3080302@barrowhillfarm.org.uk> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have a disc formatted as btrfs, on which is mounted /home.
/home/bob is a regular directory.
/home/bob/Documents is a btrfs subvolume
/home is btrfs root
If I do
# mv /home/bob /home/bob_original
# btrfs subvolume create /home/bob
# mv /home/bob_original/* /home/bob/
# rm /home/bob_original
will the original subvolume /home/bob/Documents survive this
operation, and will it now exist as a subvolume under the new
subvolume /home/bob?
I realise it's best to create subvolumes progressively from the top of
the filesystem tree, but this system originated as an ext4fs which was
migrated to btrfs, and some sensible things got missed in all the
excitement. ;-)
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 5 days 20:14, 3 users, load average: 0.00, 0.04, 0.08
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlO2vGQACgkQ0Sr7eZJrmU6CPACgoLTFUxx68+z/H30C5wd/MPe4
6rcAoKpqxoETgkbgMd+MAbHEL7BWpLBs
=Cbmm
-----END PGP SIGNATURE-----
next reply other threads:[~2014-07-04 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 14:38 Bob Williams [this message]
2014-07-04 20:38 ` A question about subvolumes 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
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=53B6BC65.3080302@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox