On Wed, Aug 29, 2018 at 5:16 AM Harald Dunkel <harald.dunkel@xxxxxxxxx> wrote: > > Hi folks, > > dmesg -T shows me a large list of messages > > : > [Wed Aug 29 11:13:02 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > [Wed Aug 29 11:13:02 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > [Wed Aug 29 11:13:02 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > [Wed Aug 29 11:13:03 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > [Wed Aug 29 11:13:03 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > [Wed Aug 29 11:13:04 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > [Wed Aug 29 11:13:05 2018] NFS: nfs4_reclaim_open_state: Lock reclaim failed! > : > > with a modification date appr 9 minutes in the future. NFS server and > client have the correct time and are in sync, afaict. How comes? Is your question about how come the timestamp is wrong or are you asking about the errors being logged. Jeff provided some info about the latter piece. However, if you are asking about the timestamps, then my guess would be that your hardware clock and your system clock might be output sync. Check the "sudo hwclock --show" to what your "date" shows. Also check the manual page that say for this option "dmesg -T" there is a warming saying that the timestamps might not be accurate. > > > Kernel is 4.9.88-1+deb9u1 on the client, 4.16.5-1~bpo9+1 on the NFS server. > > > Every helpful comment is highly appreciated. > Harri
