Feature #14145
opendelegated datasets could have better in-zone names
0%
Description
From Joyent OS-4278:
Delegated datasets are pretty great in most ways, but an unfortunate aspect of the current implementation is the name of the dataset visible within the zone. For example:
NAME USED AVAIL REFER MOUNTPOINT zones 1.26T 2.42T 768K /zones zones/66fe547a-a1b5-6e20-def1-d276ea585d05 78.2G 242G 3.03G /zones/66fe547a-a1b5-6e20-def1-d276ea585d05 zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data 75.6G 242G 25K /zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data/home 13.0M 242G 26K /home zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data/home/jclulow 12.9M 242G 12.9M /home/jclulow zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data/ws 74.6G 242G 222M /ws zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data/ws/_jmc2 68.0G 242G 68.0G /ws/_jmc2 zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data/ws/plat 6.35G 242G 6.35G /ws/plat zones/66fe547a-a1b5-6e20-def1-d276ea585d05/data/www 1.02G 242G 1.02G /var/www
Here, the delegated dataset (data) is a child of the zone dataset (zones/66fe547a-a1b5-6e20-def1-d276ea585d05
) in the global zone, as managed by vmadm
. The first two components of this dataset name, i.e. the name of the zone dataset, are generally irrelevant to the in-zone consumer of the dataset; in fact, they make it kind of a pain to inspect visually and to use.
It would be much better if we could, at least in some circumstances, provide the name of the first delegated component (i.e. data, above) and provide a virtualised view of the delegated dataset within the zone. For example, the above should really look like this:
NAME USED AVAIL REFER MOUNTPOINT data 75.6G 242G 25K /data data/home 13.0M 242G 26K /home data/home/jclulow 12.9M 242G 12.9M /home/jclulow data/ws 74.6G 242G 222M /ws data/ws/_jmc2 68.0G 242G 68.0G /ws/_jmc2 data/ws/plat 6.35G 242G 6.35G /ws/plat data/www 1.02G 242G 1.02G /var/www