Messages in this thread | | | From | Grant Coady <> | Subject | Re: 2.6.17.8 - do_vfs_lock: VFS is out of sync with lock manager! | Date | Mon, 14 Aug 2006 09:08:49 +1000 |
| |
On Fri, 11 Aug 2006 00:37:35 +0200, "Jesper Juhl" <jesper.juhl@gmail.com> wrote:
>On 09/08/06, Jesper Juhl <jesper.juhl@gmail.com> wrote: >> On 09/08/06, Grant Coady <gcoady.lk@gmail.com> wrote: >> > On Tue, 8 Aug 2006 16:39:54 +0200, "Jesper Juhl" <jesper.juhl@gmail.com> 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 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? >> > >> > I don't have an answer, but offer this observation: five boxen running >> > 2.6.17.8 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 2.6.11.11 and doesn't seem to be >> reporting any problems. But I now have two more of my webservers (both >> running 2.6.17.8) 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 2.6.17.8 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 2.6.17.8 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.
Grant. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |