> > SXCE is coming out _very_ soon. But all of your clients need > to support NFSv4 mount point crossing to make full use of it, > unless the automounter works out well enough. >
Ahh, that's a shame.. Automounter works sufficiently at the moment, but it does not work well with discovering new file-systems. The only way for it to see newly created file-systems seems to be to modify /etc/auto_master and run "automount -v" so that it re-mounts /net/x4500/. This is a shame, I would have to connect to all servers after creating an account, and hope that /net/x4500 can be remounted. # zfs create -o quota=30M -o atime=off zpool1/mail/m/e/0/0/me123456 # showmount -e | grep 123456 /export/mail/m/e/0/0/me123456 (everyone) Client: # cd /net/x4500/export/mail/m/e/0/0/me123456 # df | grep me123456 # touch /etc/auto_master && automount -v # cd /net/x4500/export/mail/m/e/0/0/me123456 # df | grep me123456 Hmm no, that is not always enough for it to realise it needs to refresh. I made the mistake of umount -f /net/x4500/export/mail, even when autofs was disabled, and now all I get is I/O Errors. Is it always this sensitive? So easy to mess up and confuse itself? I would hesitate to run automount in production if the slightest mis-use makes it fall apart, and I still can't make it see new file-systems :) Can I force it to flush/start-again somehow? I will have to play with it some more. -- 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
