From: Hugo Mills <hugo@carfax.org.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: generic name for volume and subvolume root?
Date: Sat, 9 Sep 2017 11:00:29 +0000 [thread overview]
Message-ID: <20170909110029.GF23980@carfax.org.uk> (raw)
In-Reply-To: <20170909083551.GC22060@rus.uni-stuttgart.de>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
On Sat, Sep 09, 2017 at 10:35:51AM +0200, Ulli Horlacher wrote:
> As I am writing some documentation abount creating snapshots:
> Is there a generic name for both volume and subvolume root?
>
> Example:
>
> root@fex:~# btrfs subvol show /mnt
> ERROR: not a subvolume: /mnt
>
> root@fex:~# btrfs subvol show /mnt/test
> /mnt/test is toplevel subvolume
>
> root@fex:~# btrfs subvol show /mnt/test/data
> /mnt/test/data
> Name: data
> UUID: b32a5949-dfd6-ef45-8616-34ae4cdf6fb8
> (...)
>
> root@fex:~# btrfs subvol show /mnt/test/data/sw
> ERROR: not a subvolume: /mnt/test/data/sw
>
>
> I can create snapshots of /mnt/test and /mnt/test/data, but not of /mnt
> and /mnt/test/data/sw
>
> Is there a simple name for directories I can snapshot?
Subvolume. If you can snapshot it, it's a subvolume. Some
subvolumes are also snapshots. (And all snapshots are subvolumes).
The subvolume with ID 5 (or ID 0, which is an alias) is the "top
level subvolume", and has the unique property that it can't be
renamed, deleted or replaced, where all other subvolumes can be.
Hugo.
--
Hugo Mills | Well, you don't get to be a kernel hacker simply by
hugo@... carfax.org.uk | looking good in Speedos.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Rusty Russell
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-09-09 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 8:35 generic name for volume and subvolume root? Ulli Horlacher
2017-09-09 10:40 ` Qu Wenruo
2017-09-09 10:48 ` Ulli Horlacher
2017-09-09 10:58 ` Qu Wenruo
2017-09-09 11:06 ` Hugo Mills
2017-09-09 11:13 ` Hans van Kranenburg
2017-09-09 11:00 ` Hugo Mills [this message]
2017-09-10 14:21 ` Peter Grandi
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=20170909110029.GF23980@carfax.org.uk \
--to=hugo@carfax.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