A Darren Dunham wrote: > On Tue, Sep 25, 2007 at 06:09:04PM -0700, Richard Elling wrote: >> Actually, you can use the existing name space for this. By default, >> ZFS uses /dev/dsk. But everything in /dev is a symlink. So you could >> setup your own space, say /dev/myknowndisks and use more descriptive >> names. You might need to hack on the startup service to not look at >> /dev, but that shouldn't be too hard. In other words, if the answer >> is "let the sysadmin do it" then it can be considered solved. > > It seems to me that would limit the knowledge to the currently imported > machine, not keep it with the pool.
The point is that the name of the vdev doesn't really matter to ZFS. > Naming of VxVM disks is valuable and powerful because the names are > stored in the diskgroup and are visible to any host that imports it. Ah, but VxVM has the concept of owned disks. You cannot share a disk across VxVM instances (CVM excepted) and each OS can have only one VxVM instance. OTOH, ZFS storage pools are at the vdev level, not the disk level, so ZFS is not constrained by the disk boundary. To take this discussion further, if a disk:vdev mapping is not 1:1, then how would vanity naming of disks make any difference to ZFS? -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
