[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-id: <20080215010740.GZ3029@webber.adilger.int>
Date: Thu, 14 Feb 2008 18:07:40 -0700
From: Andreas Dilger <adilger@....com>
To: "Theodore Ts'o" <tytso@....edu>
Cc: linux-ext4@...r.kernel.org
Subject: [PATCH] blkid detection for ZFS
Attached is a patch to detect ZFS in libblkid. It isn't by any means
complete, because it doesn't report the LABEL or UUID of the device,
nor names any of the constituent filesystems. The latter is quite
complex to implement and may be beyond the scope of libblkid.
Some input is welcome here also... There is a UUID (GUID) for the whole
"pool" (aggregation of devices that ZFS filesystems might live on), a
UUID for the "virtual device" (vdev) (akin to MD RAID set) that a disk
is part of and also a separate UUID for each device. There is a LABEL
(pool name) for the whole pool, but not one for an individual filesystem.
I'm thinking of making the blkid UUID be the GUID of the whole pool, as
any device in the pool would be sufficient to locate all of the component
devices. This means all devices in the same pool will return the same
UUID, but for identification that should be fine I think... I haven't
checked for pathologies in libblkid regarding that yet.
On a related note - on Solaris the ZFS filesystems always live in a GPT
partition table, and I note that libblkid doesn't identify this. Is that
something we want to start adding to libblkid (e.g. GPT, DOS, LVM, etc)?
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
View attachment "e2fsprogs-blkid-zfs.patch" of type "text/plain" (6072 bytes)
Powered by blists - more mailing lists