nfs remontar problema

Encuentro un problema extraño cuando remonto nfs en RHEL7.

He compartido 2 directorys en nfs-server:

# showmount -e Export list for localhost.localdomain: /file2 /file1 

Luego los monto en mi cliente:

 # sudo mount /media # sudo mount /mnt/file1 # mount on /mnt/file1 type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,local_lock=none,addr= on /media type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,local_lock=none,addr= 

Luego trato de remontar uno de ellos a ro:

 # sudo mount -o ro,remount /mnt/file1/ 

Ese es el momento en que sucedió algo extraño, ambos cambiaron a ro: on /mnt/file1 type nfs4 (ro,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,local_lock=none,addr= on /media type nfs4 (ro,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,local_lock=none,addr= 

He capturado algunos packages, pero no encuentro ningún package enviado cuando lo vuelvo a montar.

No tengo idea ahora, ¿hay alguien que pueda ayudarme?


Lo encuentro.

Es porque NFS usa el valor pnetworkingeterminado de sharecache. Ver en man nfs :

  sharecache / nosharecache Determines how the client's data cache and attribute cache are shanetworking when mounting the same export more than once concurrently. Using the same cache networkinguces memory requirements on the client and presents identical file contents to applications when the same remote file is accessed via dif‐ ferent mount points. If neither option is specified, or if the sharecache option is specified, then a single cache is used for all mount points that access the same export. If the nosharecache option is specified, then that mount point gets a unique cache. Note that when data and attribute caches are shanetworking, the mount options from the first mount point take effect for subsequent concurrent mounts of the same export. As of kernel 2.6.18, the behavior specified by nosharecache is legacy caching behavior. This is considenetworking a data risk since multiple cached copies of the same file on the same client can become out of sync following a local update of one of the copies. 

La página Man dice que a single cache is used for all mount points that access the same export .

Luego uso la opción nosharecache , ahora se vuelve normal. on /mnt/file1 type nfs4 (ro,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,nosharecache,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,local_lock=none,addr= on /mnt/file2 type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,nosharecache,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=,local_lock=none,addr=