Score:0

NFS4 late mounts on server are not visible to clients

cn flag

I have fairly simple working NFS version 4 setup on Ubuntu 20.04LTS with one server and few clients (all same OS). I export /mountpoint. My /etc/exports on server looks like this:

/export            *(rw,sync,no_subtree_check,fsid=0,crossmnt)
/export/mountpoint *(rw,sync,no_subtree_check,fsid=100)

I'd like to mount (either directly or via bind-mount) another filesystem into this directory when specific device becomes available on server (after NFS server already started and some clients already mounted /mountpoint). Once device becomes available I know it will stay like that until the next server reboot. Problem is that clients who mounted /mountpoint before device became available will only see the underlying filesystem even if device is already mounted to /mountpoint. If clients mount /mountpoint after device is mounted into it on server it works perfectly.

The only way I found to reflect that is to re-mount /mountpoint on such clients. I tried to play with NFS client cache but I don't think that's the problem here.

Is there any way to make this work with NFS without re-mounting /mountpoint on clients?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.