From: David Brown <btrfs@davidb.org>
To: linux-btrfs@vger.kernel.org
Subject: UUID of subvolumes
Date: Thu, 8 Apr 2010 08:51:42 -0700 [thread overview]
Message-ID: <20100408155141.GA14330@arch.davidb.org> (raw)
I am developing backup software (<http://github.com/d3zd3z/jpool> for
the curious), and have been doing some testing with btrfs.
Jpool currently uses the blkid database to map between device numbers
(st_rdev) and the uuid of a particular filesystem. I originally
created this because LVM device numbers sometimes changed. Jpool
uses the uuid to track files within a tree.
The subvolumes on btrfs seem to be getting ephemeral device numbers,
which aren't listed in the blkid output. The program falls back to
using the mountpoint, but that misses mountpoints changing.
- Do subvolumes in btrfs even have separate uuids, and should they?
- Is there any way for me to map a particular st_rdev value to a
particular filesystem/subvolume?
- btrfs seems to allow me to rename subvolumes, so this doesn't seem
like a particularly good value to use as a key. The device number
can change depending on what else might be used.
- Any other ideas on a unique key I could use for a given subvolume
to identify the files on that volume, even if it moves around?
Thanks,
David Brown
next reply other threads:[~2010-04-08 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 15:51 David Brown [this message]
2010-04-08 22:57 ` UUID of subvolumes Karel Zak
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=20100408155141.GA14330@arch.davidb.org \
--to=btrfs@davidb.org \
--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).