All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olga Kornievskaia <aglo@umich.edu>
To: harald.dunkel@aixigo.de
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: nfs4_reclaim_open_state: Lock reclaim failed!
Date: Fri, 31 Aug 2018 11:41:05 -0400	[thread overview]
Message-ID: <CAN-5tyGWO0FLZez+iyJ_EeBdmBcj=gA2iWi5TvjY+gh5pMtrXg@mail.gmail.com> (raw)
In-Reply-To: <03f45066-5cc4-b99a-edc4-69dc34592101@aixigo.de>

On Wed, Aug 29, 2018 at 5:16 AM Harald Dunkel <harald.dunkel@aixigo.de> 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

  parent reply	other threads:[~2018-08-31 19:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29  9:09 nfs4_reclaim_open_state: Lock reclaim failed! Harald Dunkel
2018-08-29  9:13 ` Harald Dunkel
2018-08-31 11:49   ` Jeff Layton
2018-09-03  8:34     ` Harald Dunkel
2018-09-03  9:32       ` Jeff Layton
2018-09-04  7:31         ` Harald Dunkel
2018-09-04 12:11           ` Jeff Layton
2018-08-31 15:41 ` Olga Kornievskaia [this message]
2018-09-03  7:48   ` Harald Dunkel
2018-09-03 13:15     ` Olga Kornievskaia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN-5tyGWO0FLZez+iyJ_EeBdmBcj=gA2iWi5TvjY+gh5pMtrXg@mail.gmail.com' \
    --to=aglo@umich.edu \
    --cc=harald.dunkel@aixigo.de \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.