Typically, that happens when you have a filesystem mounted in /export
and the (zfs-)fuse daemon dies.
> I have reviewed some forums online and I have been unable to resolve
> this previously. Any insight provided would be much appreciated.
It's hard to diagnose the problem without more information.
Can you check to see if 'df' also reports "transport endpoint not
connected" on that filesystem as it usually does?
Are there other ZFS filesystems mounted at that time?
Usually, you can clear that error by doing "umount /export". Then check
"df" to see if you have cleared all such errors.
Once you've cleared all such errors, make sure you don't have the
zfs-fuse daemon running by doing "zfs umount -a" and "killall
zfs-fuse" (you may get an error in "zfs umount -a" if the zfs-fuse
daemon was not running).
After that, go to your zfs-fuse tree and do:
1) cd src/zfs-fuse
2) ./run.sh
On another terminal:
3) zfs mount -a
4) cd /export
If you get the same error, then it means the zfs-fuse daemon died and
should have left a core file in $ZFS_FUSE/src/zfs-fuse.
You can then provide more information by following steps 4 and 5
described in the BUGS file that comes with zfs-fuse.
Thanks,
Ricardo