The RFE is 4107375 Automounter should be able to detect changes in the
exported file systems
A simple workaround which does not require root credentials is to change
the server name - the cache is case sensitive. If the server hostname
has 8 letter, we have 256 options. Any such access will get a new, fresh
list of exports. E.g.
$ ls /net/jurassic
$ ls /net/Jurassic
$ ls /net/JurAssic
$ ls /net/JURASSIC
or
$ ls /net/129.146.17.63
$ ls /net/jurassic.sfbay
This is not scriptable and scalable workaround, but can be the easiest
(and for unprivileged user the only) to access the new shares.
Pavel
On 03/25/10 16:48, Gordon Ross wrote:
This is probably an old problem, but I'm wondering if anyone knows of a
work-around? Or maybe an RFE?
When your NFS client has some (lets say) ZFS exports mounted, i.e.
/net/server/tank
/net/server/tank/a
/net/server/tank/b
Then on the server I create /tank/c and it gets an NFS export,
as shown by "showmount -e server". However, if the client
has activity in /net/server/tank/a there does not seem to be
any way to force the client to reexamine the exports, so any
access to /net/server/tank/c forever fails.
Is there a way around that?
Thanks,
Gordon
_______________________________________________
nfs-discuss mailing list
[email protected]
