I am still having issues with lofs even. I have created 2329 home directories, each with a "mail" directory inside it.
zfs original: /export/mail/ lofs mount: /export/test/ # find /export/test/mail/m/e/0/0/ -name mail | wc -l 2327 NFS client: mount /export/test/ # ls -l /export/test/mail/m/e/0/0 drwxr-xr-x 2 root root 2 Nov 29 12:13 me649000 [snip] # ls -l /export/test/mail/m/e/0/0 | wc -l 2328 # find /export/test/mail/m/e/0/0/ -name mail | wc -l 0 So I create the three following file-systems, directories: drwxr-xr-x 3 root root 3 Nov 29 12:17 this_is_a_local_dir drwxr-xr-x 3 root root 3 Nov 29 12:18 zfs_without_quota drwxr-xr-x 3 root root 3 Nov 29 12:19 zfs_without_compression As seen from the NFS client: drwxr-xr-x 3 root root 3 Nov 29 12:17 this_is_a_local_dir drwxr-xr-x 2 root root 2 Nov 29 12:19 zfs_without_compression drwxr-xr-x 2 root root 2 Nov 29 12:18 zfs_without_quota NFS client: find /export/test/m/e/0/0/ -name mail -ls 4455 2 drwxr-xr-x 2 root root 2 Nov 29 12:17 /export/test/m/e/0/0/this_is_a_local_dir/mail So, even though the lofs mounted filesystem works just fine on the x4500 machine itself, once it is NFS exported, I can not enter other ZFS file-systems inside that directory tree. All those file-systems just appear empty. I also found this situation to be confusing: x4500: # cd zfs_without_quota # mkdir test # ls -l drwxr-xr-x 2 root root 2 Nov 29 12:18 mail drwxr-xr-x 2 root root 2 Nov 29 12:28 test NFS client: # cd zfs_without_quota # mkdir foo # ls -l drwxr-xr-x 2 root root 2 Nov 29 12:28 foo x4500: # ls -l drwxr-xr-x 2 root root 2 Nov 29 12:18 mail drwxr-xr-x 2 root root 2 Nov 29 12:28 test Sooo.. what? Where did that "foo" directory get created exactly? # pwd /export/test/m/e/0/0/zfs_without_quota # df -h . Filesystem size used avail capacity Mounted on x4500:/export/test 17T 4.6M 17T 1% /export/test Jorgen Lundman wrote: > Ah it's a somewhat mis-leading error message: > > bash-3.00# mount -F lofs /zpool1/test /export/test > bash-3.00# share -F nfs -o rw,anon=0 /export/test > Could not share: /export/test: invalid path > bash-3.00# umount /export/test > bash-3.00# zfs set sharenfs=off zpool1/test > bash-3.00# mount -F lofs /zpool1/test /export/test > bash-3.00# share -F nfs -o rw,anon=0 /export/test > > So if any zfs file-system has sharenfs enabled, you will get "invalid > path". If you disable sharenfs, then you can export the lofs. > > Lund > > > J.P. King wrote: >>> I can not export lofs on NFS. Just gives invalid path, >> Tell that to our mirror server. >> >> -bash-3.00$ /sbin/mount -p | grep linux >> /data/linux - /linux lofs - no ro >> /data/linux - /export/ftp/pub/linux lofs - no ro >> -bash-3.00$ grep linux /etc/dfs/sharetab >> /linux - nfs ro Linux directories >> -bash-3.00$ df -k /linux >> Filesystem 1K-blocks Used Available Use% Mounted on >> data 3369027462 3300686151 68341312 98% /data >> >>> and: >>> >>> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6578437 >> I'm using straight Solaris, not Solaris Express or equivalents: >> >> -bash-3.00$ uname -a >> SunOS leprechaun.csi.cam.ac.uk 5.10 Generic_127111-01 sun4u sparc >> SUNW,Sun-Fire-V240 Solaris >> >> I can't comment on the bug, although I notice it is categorised under >> nfsv4, but the description doesn't seem to match that. >> >>> Jorgen Lundman | <[EMAIL PROTECTED]> >> Julian >> -- >> Julian King >> Computer Officer, University of Cambridge, Unix Support >> > -- Jorgen Lundman | <[EMAIL PROTECTED]> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home) _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
