From: Hugo Mills <hugo@carfax.org.uk>
To: Richard Hughes <hughsient@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Naming of subvolumes
Date: Thu, 25 Oct 2012 14:28:25 +0100 [thread overview]
Message-ID: <20121025132825.GD25498@carfax.org.uk> (raw)
In-Reply-To: <1351168220.1923.6.camel@hughsie-work.lan>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On Thu, Oct 25, 2012 at 01:30:20PM +0100, Richard Hughes wrote:
> I'm planning to use "btrfs subvolume snapshot -r <name>" in the system
> upgrade functionality[1] if the user is using btrfs for their root file
> system. We've got most of the bits in place already for Fedora 18.
>
> One think that confuses me is the convention for the naming of
> snapshots. Is there any conventions or prior art there? Can I add
> metadata to the snapshot so that I don't have encode everything in the
> snapshot name itself?
How about user xattrs? IIRC, that's the user.* namespace.
The only convention I'm aware of is Ubuntu's use of an @
substitution, where the subvolume to be mounted at / is called @, and
the subvolume to be mounted at /home becomes @home. Both of those
subvolumes are stored in the (otherwise empty) top-level of the
filesystem, which is not mounted in normal operation.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- This chap Anon is writing some perfectly lovely stuff ---
at the moment.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-10-25 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 12:30 Naming of subvolumes Richard Hughes
2012-10-25 13:18 ` anand jain
2012-10-25 13:28 ` Hugo Mills [this message]
2012-10-25 13:44 ` Richard Hughes
[not found] ` <CAAeznTr6AvqbJ+WOw6S5kyW2_qbSUQgJfAO88m9KdV+3PyGUcw@mail.gmail.com>
2012-10-25 15:16 ` Richard Hughes
2012-10-25 15:59 ` Calvin Walton
2012-10-25 17:19 ` Richard Hughes
2012-10-26 5:24 ` Chris Murphy
2012-10-26 8:27 ` Richard Hughes
2012-10-26 15:54 ` Chris Murphy
2012-10-27 1:58 ` cwillu
2012-10-27 3:03 ` Fajar A. Nugraha
2012-10-27 17:22 ` Naming of (bootable) subvolumes Chris Murphy
2012-10-28 9:25 ` Goffredo Baroncelli
2012-10-28 16:57 ` Chris Murphy
2012-10-28 9:38 ` Fajar A. Nugraha
2012-10-27 16:08 ` Naming of subvolumes Chris Murphy
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=20121025132825.GD25498@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=hughsient@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.