From: Hugo Mills <hugo@carfax.org.uk>
To: pubny@xs4all.nl
Cc: linux-btrfs@vger.kernel.org
Subject: Re: "@" prefix in subvolume paths
Date: Wed, 10 Jun 2015 23:10:14 +0000 [thread overview]
Message-ID: <20150610231014.GF18226@carfax.org.uk> (raw)
In-Reply-To: <20150609195505.12ace1e8@host22323.xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 2517 bytes --]
On Tue, Jun 09, 2015 at 07:55:05PM +0200, pubny@xs4all.nl wrote:
> Hi,
>
> I've noticed this "@" sign in the subvolume's path with SLES12. I'm
> wondering what is its purpose. openSUSE 13.2 doesn't seem to be using
> it.
They created a subvolume called "@" and then put all the other
subvolumes under there. There's nothing special about it.
The @ is often used as a prefix on subvolumes (e.g. in Ubuntu) to
indicate that they're subvolumes, but it's not required, and doesn't
have any extra meaning beyond being a useful naming convention.
Hugo.
> Thanks,
> Gábor
>
>
> SLES12:
> # btrfs sub list /
> ID 257 gen 2270 top level 5 path @
> ID 258 gen 1655 top level 257 path @/boot/grub2/i386-pc
> ID 259 gen 4263 top level 257 path @/boot/grub2/x86_64-efi
> ID 260 gen 4037 top level 257 path @/opt
> ID 261 gen 2553 top level 257 path @/srv
> ID 262 gen 4521 top level 257 path @/tmp
> ID 263 gen 4492 top level 257 path @/usr/local
> ID 264 gen 1655 top level 257 path @/var/crash
> ID 265 gen 1655 top level 257 path @/var/lib/mailman
> ID 266 gen 1655 top level 257 path @/var/lib/named
> ID 267 gen 1655 top level 257 path @/var/lib/pgsql
> ID 268 gen 4523 top level 257 path @/var/log
> ID 269 gen 1655 top level 257 path @/var/opt
> ID 270 gen 4524 top level 257 path @/var/spool
> ID 271 gen 4521 top level 257 path @/var/tmp
> ID 275 gen 4505 top level 257 path @/.snapshots
>
>
> openSUSE 13.2:
>
> # btrfs subvol list /
> ID 257 gen 3481911 top level 5 path boot/grub2/i386-pc
> ID 258 gen 3481911 top level 5 path boot/grub2/x86_64-efi
> ID 259 gen 3517714 top level 5 path home
> ID 260 gen 3515789 top level 5 path opt
> ID 261 gen 3513493 top level 5 path srv
> ID 262 gen 3513372 top level 5 path tmp
> ID 263 gen 3517660 top level 5 path usr/local
> ID 264 gen 3513372 top level 5 path var/crash
> ID 265 gen 3513372 top level 5 path var/lib/mailman
> ID 266 gen 3513372 top level 5 path var/lib/named
> ID 267 gen 3513372 top level 5 path var/lib/pgsql
> ID 268 gen 3517714 top level 5 path var/log
> ID 269 gen 3513372 top level 5 path var/opt
> ID 270 gen 3517714 top level 5 path var/spool
> ID 271 gen 3517706 top level 5 path var/tmp
> ID 276 gen 3517669 top level 5 path .snapshots
--
Hugo Mills | ... one ping(1) to rule them all, and in the
hugo@... carfax.org.uk | darkness bind(2) them.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Illiad
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2015-06-10 23:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 17:55 "@" prefix in subvolume paths pubny
2015-06-10 23:10 ` Hugo Mills [this message]
2015-06-10 23:37 ` gny
2015-06-11 1:50 ` Jeff Mahoney
2015-06-11 9:02 ` Dimitri John Ledkov
2015-06-15 8:53 ` Gábor Nyers
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=20150610231014.GF18226@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=pubny@xs4all.nl \
/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