![]() | |||||||||||||
Messages in this thread |
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. 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/ | ||||||||||||
| Last update: 2006-08-09 07:57 [from the cache] ©2003-2008 | |||||||||||||