From: Richard Hughes <hughsient@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Naming of subvolumes
Date: Thu, 25 Oct 2012 14:44:13 +0100 [thread overview]
Message-ID: <1351172653.1923.10.camel@hughsie-work.lan> (raw)
In-Reply-To: <20121025132825.GD25498@carfax.org.uk>
On Thu, 2012-10-25 at 14:28 +0100, Hugo Mills wrote:
> How about user xattrs? IIRC, that's the user.* namespace.
Yes, but we still need some kind of metadata standard. For instance, I
might want to put a list of packages that were changed in the metadata
so that admins know why the snapshot was created. It's highly likely
distros like Ubuntu won't want to do it using the same mechanism (i.e.
using PackageKit) but having some shared specs is probably a good idea.
> 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.
That could work I suppose.
> Both of those
> subvolumes are stored in the (otherwise empty) top-level of the
> filesystem, which is not mounted in normal operation.
If we do one upgrade a week, that's 52 subvolumes cluttering things up.
Should the subvolumes be placed somewhere upgrade specific? Any best
practice ideas on naming? e.g. @system-upgrade-20121025?
Richard
next prev parent reply other threads:[~2012-10-25 13:41 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
2012-10-25 13:44 ` Richard Hughes [this message]
[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=1351172653.1923.10.camel@hughsie-work.lan \
--to=hughsient@gmail.com \
--cc=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 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.