From: Richard Hughes <hughsient@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Naming of subvolumes
Date: Thu, 25 Oct 2012 13:30:20 +0100 [thread overview]
Message-ID: <1351168220.1923.6.camel@hughsie-work.lan> (raw)
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?
Also, being able to do a snapshot using a libbtrfs (or whatever) would
be much preferable to exec'ing the btrfs command and then trying to
parse the exit code and any stderr. I don't know if this kind of thing
is the norm for filesystem utilities, but a versioned shared library to
use would be awesome.
Any advice welcome, thanks.
Richard
(PackageKit author)
[1] https://fedoraproject.org/wiki/Features/OfflineSystemUpdates
next reply other threads:[~2012-10-25 12:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 12:30 Richard Hughes [this message]
2012-10-25 13:18 ` Naming of subvolumes anand jain
2012-10-25 13:28 ` Hugo Mills
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=1351168220.1923.6.camel@hughsie-work.lan \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).