Hi. Do you have some known limitation(or bugs) related to NFS-exporting of HAMMER filesystem? I've been playing with /etc/exports so as I can upgrade my router to 2.0, and found something strange:
- can't NFS-mount an exported directory inside a HAMMER filesystem, only root directory can be NFS-mounted (no errors from mountd though) - can't NFS-mount an exported pseudofs (Permission denied), or NFS-mount a pseudofs inside an exported HAMMER filesystem (again, no errors from mountd) - I can mount it read-only, but accessing a pfs gives me `File too large' that is: # ls -l /HAMMER lrwxr-xr-x 1 root wheel 10 Jul 18 12:31 obj -> @@0xffffffffffffffff:00003 # grep /HAMMER /HAMMER -ro -mapall=dragonfly # /etc/rc.d/mountd reload (no errors on /var/log/messages) # mount 127.0.0.1:/HAMMER /mnt # ls -l /mnt total 0 ls: /mnt/obj: File too large lrwxr-xr-x 1 root wheel 10 Jul 18 12:31 obj - a regular symlink takes forever to appear in the NFS-mounted directory even though it's accessible from that directory: # umount /mnt # mount 127.0.0.1:/HAMMER /mnt # mkdir /HAMMER/foo; ln -s foo /HAMMER/symlink; sync # ls -l /mnt total 0 drwxr-xr-x 1 root wheel 0 Jul 19 09:35 foo ls: /mnt/obj: File too large lrwxr-xr-x 1 root wheel 10 Jul 18 12:31 obj # ls -l /mnt/symlink lrwxr-xr-x 1 root wheel 3 Jul 19 09:36 /mnt/symlink -> foo # ls -dlL /mnt/symlink drwxr-xr-x 1 root wheel 0 Jul 19 09:35 /mnt/symlink # umount /mnt # mount 127.0.0.1:/HAMMER /mnt # ls -l /mnt total 0 drwxr-xr-x 1 root wheel 0 Jul 19 09:35 foo ls: /mnt/obj: File too large lrwxr-xr-x 1 root wheel 10 Jul 18 12:31 obj lrwxr-xr-x 1 root wheel 3 Jul 19 09:36 symlink -> foo Thanks.
