Re: [zfs-discuss] Nested ZFS file systems are not visible over an NFS export
Sriram, sharenfs is an inherited property. Looks like in your case you set the sharenfs=on on datapool/vmwarenfs after the underlying filesystems were created. If you had set the sharenfs=on before creating the underlying filesystems, then the property would have been inherited by the children and hence they would be shared as well. I guess that would help in your case. Hope that helps. Thanks and regards, Sanjeev On Sun, Feb 08, 2009 at 12:43:26AM +0530, Sriram Narayanan wrote: An update: I'm using VMWare ESX 3.5 and VMWare ESXi 3.5 as the NFS clients. I'm use zfs set sharenfs=on datapool/vmwarenfs to make that zfs file system accessible over NFS. -- Sriram On Sun, Feb 8, 2009 at 12:07 AM, Sriram Narayanan sriram...@gmail.com wrote: Hello: I have the following zfs structure datapool/vmwarenfs - which is available over NFS I have some ZFS filesystems as follows: datapool/vmwarenfs/basicVMImage datapool/vmwarenfs/basicvmim...@snapshot datapool/vmwarenfs/VMImage01- zfs cloned from basicvmim...@snapshot datapool/vmwarenfs/VMImage02- zfs cloned from basicvmim...@snapshot These are accessible via NFS as /datapool/vmwarenfs with the subfolders VMImage01 and VMImage02 What's happening right now: a. When I connect to datapool/vmwarenfs over NFS, - the contents of /datapool/vmwarenfs are visible and usable - VMImage01 and VMImage02 are appearing as empty sub-folders at the paths /datapool/vmwarenfs/VMImage01 and /datapool/vmwarenfs/VMImage02, but their contents are not vbisible. b. When I explicity share VMImage01 and VMImage02 via NFS, then /datapool/vmwarenfs/VMImage01 - usable as a separate NFS share /datapool/vmwarenfs/VMImage02 - usable as a separate NFS share What I'd like to have: - attach over NFS to /datapool/vmwarenfs - view the ZFS filesystems VMImage01 and VMImage02 as sub folders under /datapool/vmwarenfs If needed, I can move VMImage01 and VMImage02 from datapool/vmwarenfs, and even re-create them elsewhere. -- Sriram ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Nested ZFS file systems are not visible over an NFS export
An update: I'm using VMWare ESX 3.5 and VMWare ESXi 3.5 as the NFS clients. I'm use zfs set sharenfs=on datapool/vmwarenfs to make that zfs file system accessible over NFS. -- Sriram On Sun, Feb 8, 2009 at 12:07 AM, Sriram Narayanan sriram...@gmail.com wrote: Hello: I have the following zfs structure datapool/vmwarenfs - which is available over NFS I have some ZFS filesystems as follows: datapool/vmwarenfs/basicVMImage datapool/vmwarenfs/basicvmim...@snapshot datapool/vmwarenfs/VMImage01- zfs cloned from basicvmim...@snapshot datapool/vmwarenfs/VMImage02- zfs cloned from basicvmim...@snapshot These are accessible via NFS as /datapool/vmwarenfs with the subfolders VMImage01 and VMImage02 What's happening right now: a. When I connect to datapool/vmwarenfs over NFS, - the contents of /datapool/vmwarenfs are visible and usable - VMImage01 and VMImage02 are appearing as empty sub-folders at the paths /datapool/vmwarenfs/VMImage01 and /datapool/vmwarenfs/VMImage02, but their contents are not vbisible. b. When I explicity share VMImage01 and VMImage02 via NFS, then /datapool/vmwarenfs/VMImage01 - usable as a separate NFS share /datapool/vmwarenfs/VMImage02 - usable as a separate NFS share What I'd like to have: - attach over NFS to /datapool/vmwarenfs - view the ZFS filesystems VMImage01 and VMImage02 as sub folders under /datapool/vmwarenfs If needed, I can move VMImage01 and VMImage02 from datapool/vmwarenfs, and even re-create them elsewhere. -- Sriram ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Nested ZFS file systems are not visible over an NFS export
This is not a ZFS question. It is an NFS question. For Solaris NFSv4 clients post-b77, they will follow the mounts, via a method called mirror mounts. For other NFS clients, the behaviour will be that which the developers implemented. Please consult the appropriate NFS client forum for your system. The announcement of mirror mounts for Solaris is here: http://opensolaris.org/os/community/on/flag-days/pages/2007102201/ -- richard Sriram Narayanan wrote: An update: I'm using VMWare ESX 3.5 and VMWare ESXi 3.5 as the NFS clients. I'm use zfs set sharenfs=on datapool/vmwarenfs to make that zfs file system accessible over NFS. -- Sriram On Sun, Feb 8, 2009 at 12:07 AM, Sriram Narayanan sriram...@gmail.com wrote: Hello: I have the following zfs structure datapool/vmwarenfs - which is available over NFS I have some ZFS filesystems as follows: datapool/vmwarenfs/basicVMImage datapool/vmwarenfs/basicvmim...@snapshot datapool/vmwarenfs/VMImage01- zfs cloned from basicvmim...@snapshot datapool/vmwarenfs/VMImage02- zfs cloned from basicvmim...@snapshot These are accessible via NFS as /datapool/vmwarenfs with the subfolders VMImage01 and VMImage02 What's happening right now: a. When I connect to datapool/vmwarenfs over NFS, - the contents of /datapool/vmwarenfs are visible and usable - VMImage01 and VMImage02 are appearing as empty sub-folders at the paths /datapool/vmwarenfs/VMImage01 and /datapool/vmwarenfs/VMImage02, but their contents are not vbisible. b. When I explicity share VMImage01 and VMImage02 via NFS, then /datapool/vmwarenfs/VMImage01 - usable as a separate NFS share /datapool/vmwarenfs/VMImage02 - usable as a separate NFS share What I'd like to have: - attach over NFS to /datapool/vmwarenfs - view the ZFS filesystems VMImage01 and VMImage02 as sub folders under /datapool/vmwarenfs If needed, I can move VMImage01 and VMImage02 from datapool/vmwarenfs, and even re-create them elsewhere. -- Sriram ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
