Re: 126.96.36.199 - do_vfs_lock: VFS is out of sync with lock manager!
From: Grant Coady
Date: Sun Aug 13 2006 - 19:06:46 EST
On Fri, 11 Aug 2006 00:37:35 +0200, "Jesper Juhl" <jesper.juhl@xxxxxxxxx> wrote:
>On 09/08/06, Jesper Juhl <jesper.juhl@xxxxxxxxx> wrote:
>> On 09/08/06, Grant Coady <gcoady.lk@xxxxxxxxx> wrote:
>> > 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 188.8.131.52 and since the upgrade
>> > >the message started appearing.
>> > >The servers were previously running 184.108.40.206 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?
>> > I don't have an answer, but offer this observation: five boxen running
>> > 220.127.116.11 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 18.104.22.168 and doesn't seem to be
>> reporting any problems. But I now have two more of my webservers (both
>> running 22.214.171.124) 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.
>Today 3 more of my webservers running 126.96.36.199 reported this message.
>The machines all seem to be running fine still, so it doesn't seem to
>be a serious problem, but it would still be nice to get it fixed ;)
I'm running continuous kernel 2.4.33 rebuild from make mrproper plus
another console extracting tarball, diff tree against last_extracted,
on pair of 188.8.131.52 boxen overnight with NFS TCP support, no problems,
now testing without TCP support. Report again only if I see problems.
Let me know if you want to see test scripts.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/