From: Karel Zak <kzak@redhat.com>
To: David Brown <btrfs@davidb.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: UUID of subvolumes
Date: Fri, 9 Apr 2010 00:57:05 +0200 [thread overview]
Message-ID: <20100408225705.GJ7858@nb.net.home> (raw)
In-Reply-To: <20100408155141.GA14330@arch.davidb.org>
On Thu, Apr 08, 2010 at 08:51:42AM -0700, David Brown wrote:
> 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?
I think yes, in libblkid code is:
blkid_probe_set_uuid(pr, bfs->fsid);
blkid_probe_set_uuid_as(pr, bfs->dev_item.uuid, "UUID_SUB");
so there should be two UUIDs for the device.
However, I'd like to see more information about btrfs UUIDs.
BTW, see my old discussion with Andreas about UUIDs:
http://marc.info/?l=linux-fsdevel&m=126754081900406&w=2
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2010-04-08 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 15:51 UUID of subvolumes David Brown
2010-04-08 22:57 ` Karel Zak [this message]
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=20100408225705.GJ7858@nb.net.home \
--to=kzak@redhat.com \
--cc=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).