On 09/08/06, Grant Coady <gcoady.lk@xxxxxxxxx> wrote:Today 3 more of my webservers running 220.127.116.11 reported this message.
> On Tue, 8 Aug 2006 16:39:54 +0200, "Jesper Juhl" <jesper.juhl@xxxxxxxxx> wrote:
> >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 18.104.22.168 and since the upgrade
> >the message started appearing.
> >The servers were previously running 22.214.171.124 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
> >Is there anything I can do to help track down this issue?
> I don't have an answer, but offer this observation: five boxen running
> 126.96.36.199 doing six simultaneous
> bzcat /home/share/linux-2.6/patch-2.6.18-rc4.bz2|patch -p1
> didn't burp. The /home/share/ is an NFS export from another box running
> 2.4.33-rc3a, me not sure if this was exercising any NFS locking as the
> NFS source file was only opened for non-exclusive read-only.
The NFS server here is running 188.8.131.52 and doesn't seem to be
reporting any problems. But I now have two more of my webservers (both
running 184.108.40.206) that have started to complain about "do_vfs_lock:
VFS is out of sync with lock manager!"
I've not found a way to cause the message to be repported at will unfortunately.