Re: [zones-discuss] Using ZFS dataset...
Wee Yeh Tan wrote: Is there anywhere I can read about the design decisions over this? Why is inherited an issue when used in zones? I am not completely sure why this test was coded this way. I would have to try to talk to the ZFS engineer who did the original work and see if he remembers why he coded it this way. Ideally this would be documented somewhere but it is probably too low-level to have been captured and there is no comment in the code explaining the reasoning. However, I can probably guess why it was coded this way. My guess would be that the idea for a delegated dataset is that you are giving up most of the control of the dataset from the global zone administrator to the non-global zone administrator. Only the quota control is retained in the global zone. So, if you have a data set that you have explicitly set up in the global zone to mount in a non-default way, then you should not be allowed to delegate that dataset to the non-global zone. This is my best guess for why the code does this test. I'll see if I can get a better answer to this question. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Using ZFS dataset...
On 7/18/06, Jerry Jelinek <[EMAIL PROTECTED]> wrote: I am not sure what the complete sequence of commands is that you have run to cause this problem. However, the basic issue is that the mountpoint property cannot be inherited when you have zfs datasets that are configured for use in a zone. You can see all of the properties, and their source, for your filesystem by running "zfs get all pool/solarisC/dataset". If the mountpoint property shows as "inherited from XXX", then you cannot import that dataset into the zone. Jerry, Thanks for the quick response. You are right on the money that the mountpoint property was indeed inherited rather than local. The error message makes a lot more sense now. I thought it was complaining that zoneadm failed to inherit the mountpoint. Is there anywhere I can read about the design decisions over this? Why is inherited an issue when used in zones? -- Just me, Wire ... ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] Using ZFS dataset...
Wee Yeh Tan wrote: I encounter a pretty perplexing issue with using ZFS dataset in zones on S10u2 on a Sun x4100. I set up my zone in a zfs filesystem (say pool/solarisC) and inherit the dataset pool/solarisC/dataset. The zone occassionally gives me: [EMAIL PROTECTED]:~# zfs create pool/solarisC/dataset [EMAIL PROTECTED]:~# zfs list -r pool/solarisC NAME USED AVAIL REFER MOUNTPOINT pool/solarisC 23.4M 35.7G 81.5M /zones/solarisC pool/solarisC/dataset 24.5K 35.7G 24.5K /zones/solarisC/dataset [EMAIL PROTECTED]:~# zoneadm -z solarisC boot cannot verify zfs dataset pool/solarisC/dataset: mountpoint cannot be inherited zoneadm: zone solarisC failed to verify But if I set the mountpoint to something else and then back to /zones/solarisC/dataset, the zone boots and gets the dataset. The zonecfg is as follows: [EMAIL PROTECTED]:~# zonecfg -z solarisC info zonepath: /zones/solarisC autoboot: false pool: inherit-pkg-dir: dir: /lib inherit-pkg-dir: dir: /platform inherit-pkg-dir: dir: /sbin inherit-pkg-dir: dir: /usr inherit-pkg-dir: dir: /opt net: address: 172.18.183.45 physical: e1000g0 dataset: name: pool/solarisC/dataset I wonder if I am doing anything wrong. Also, why the difference in behaviour? I am not sure what the complete sequence of commands is that you have run to cause this problem. However, the basic issue is that the mountpoint property cannot be inherited when you have zfs datasets that are configured for use in a zone. You can see all of the properties, and their source, for your filesystem by running "zfs get all pool/solarisC/dataset". If the mountpoint property shows as "inherited from XXX", then you cannot import that dataset into the zone. Jerry ___ zones-discuss mailing list zones-discuss@opensolaris.org
[zones-discuss] Using ZFS dataset...
I encounter a pretty perplexing issue with using ZFS dataset in zones on S10u2 on a Sun x4100. I set up my zone in a zfs filesystem (say pool/solarisC) and inherit the dataset pool/solarisC/dataset. The zone occassionally gives me: [EMAIL PROTECTED]:~# zfs create pool/solarisC/dataset [EMAIL PROTECTED]:~# zfs list -r pool/solarisC NAME USED AVAIL REFER MOUNTPOINT pool/solarisC 23.4M 35.7G 81.5M /zones/solarisC pool/solarisC/dataset 24.5K 35.7G 24.5K /zones/solarisC/dataset [EMAIL PROTECTED]:~# zoneadm -z solarisC boot cannot verify zfs dataset pool/solarisC/dataset: mountpoint cannot be inherited zoneadm: zone solarisC failed to verify But if I set the mountpoint to something else and then back to /zones/solarisC/dataset, the zone boots and gets the dataset. The zonecfg is as follows: [EMAIL PROTECTED]:~# zonecfg -z solarisC info zonepath: /zones/solarisC autoboot: false pool: inherit-pkg-dir: dir: /lib inherit-pkg-dir: dir: /platform inherit-pkg-dir: dir: /sbin inherit-pkg-dir: dir: /usr inherit-pkg-dir: dir: /opt net: address: 172.18.183.45 physical: e1000g0 dataset: name: pool/solarisC/dataset I wonder if I am doing anything wrong. Also, why the difference in behaviour? -- Just me, Wire ... ___ zones-discuss mailing list zones-discuss@opensolaris.org
