7 Posts

October 11th, 2018 09:00

Hi,

We do have NFSv4 behavioural changes on 8.0.0.7 after client kernel updates from 3.10.0-693.21.1 to 3.10.0-862.2.3 (and higher). It's currently under investigation by EMC support but the behaviour is somewhat different and is not caused by rolling reboots (directly, at least, not impossible a longer term effect). In our case file access can start to hang on what appears a race condition forming a loop. Only by blocking access to the file entirely or rebooting client the loops are resolved.

Example syslog entry in such case: nfs4_reclaim_open_state: Lock reclaim failed!

We do see NFS4ERR_STALE_CLIENTID and  PUTFH Status: NFS4ERR_BADHANDLE entry in the exchange at the exact time.

Again, not sure if it's related but mentioning the exact same kernel is interesting. The other commonality might  the presence of multiple mounts leading to different nodes (round robin) perhaps similar to rolling from one node to another as far as the effect goes.

I hope to delve into more specifics later if needed.

No Events found!

Top