From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Cc: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
nfs@lists.sourceforge.net
Subject: 2.6.17.8 - do_vfs_lock: VFS is out of sync with lock manager!
Date: Tue, 8 Aug 2006 16:39:54 +0200 [thread overview]
Message-ID: <9a8748490608080739w2e14e5ceg44a7bf0a3b475704@mail.gmail.com> (raw)
I have some webservers that have recently started reporting the
following message in their logs :
do_vfs_lock: VFS is out of sync with lock manager!
The serveres kernels were upgraded to 2.6.17.8 and since the upgrade
the message started appearing.
The servers were previously running 2.6.13.4 without experiencing this problem.
Nothing has changed except the kernel.
I've googled a bit and found this mail
(http://lkml.org/lkml/2005/8/23/254) from Trond saying that
"The above is a lockd error that states that the VFS is failing to track
your NFS locks correctly".
Ok, but that doesn't really help me resolve the issue. The servers are
indeed running NFS and access their apache DocumentRoots from a NFS
mount.
Is there anything I can do to help track down this issue?
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next reply other threads:[~2006-08-08 14:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 14:39 Jesper Juhl [this message]
2006-08-09 5:53 ` Grant Coady
2006-08-09 8:07 ` Jesper Juhl
2006-08-10 22:37 ` Jesper Juhl
2006-08-11 0:30 ` Grant Coady
2006-08-13 23:08 ` Grant Coady
2006-08-17 6:49 ` [NFS] " Neil Brown
2006-08-17 9:58 ` Jesper Juhl
2006-08-21 3:34 ` Neil Brown
2006-08-21 19:54 ` Trond Myklebust
2006-11-21 12:43 ` Jesper Juhl
2006-11-27 9:19 ` Jesper Juhl
2007-01-29 5:08 ` Neil Brown
2007-01-29 14:16 ` Trond Myklebust
2007-01-30 23:42 ` Jesper Juhl
2007-02-01 22:39 ` Neil Brown
2006-08-12 8:58 Chuck Ebbert
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=9a8748490608080739w2e14e5ceg44a7bf0a3b475704@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®