> Reading through the doc (3.2.1.4), I see that > examples and discussions of handling zone allocated > zfs datasets via zonecfg add fs options, but I don't > see reference to zone allocated zfs datasets via > zonecfg add dataset options (where a zone priv user > is given authorization to subdivide the allocation > into new zfs objects private to the zone). >
The -u option has been changed to be more simple and when provided will tell libbe to retain the source BE's zones datasets when creating the target BE's zones datasets. If -u is not provided then individual zones datasets found in the source BE will not be created on the target BE. > I just want to make sure that Snap Upgrade will be > able to preserve a zone's zfs allocation of space and > objects when given via add dataset. Good point. libbe will have to detect the zfs "reservation" property and set up the zones dataset(s) to include a reservation value when creating the dataset. > > I was also curious if future zfs encryption efforts > would have any impact on needed beadm cli options and > managing mounts of encrypted zfs datasets holding > aBEs. Since its target delivery date will be near Snap's initial delivery date, no support for zfs encryption will be provided by beadm for the Spring release. Thanks Tim > > /jason -- This message posted from opensolaris.org
