Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750729AbWHJWhi (ORCPT ); Thu, 10 Aug 2006 18:37:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750746AbWHJWhi (ORCPT ); Thu, 10 Aug 2006 18:37:38 -0400 Received: from nf-out-0910.google.com ([64.233.182.186]:29579 "EHLO nf-out-0910.google.com") by vger.kernel.org with ESMTP id S1750729AbWHJWhh (ORCPT ); Thu, 10 Aug 2006 18:37:37 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nMfVnHYHBfDD+QrfUHM+HTuQ5AtZz47lnoAcoyVI+MvvrNYvAVPWvWfRkTThMmB2uGKMj1ZdPJDZ3JmMgtyJy/SJsI8/+7XZU20I8xheOhHI6YndajXHkKCVGPCCuSoKae5IJOABe1FB9fH2pbKv+2i/Tr1nWV7gHs7imk3Np5o= Message-ID: <9a8748490608101537y4c377fb3xcd8babbdbc29cee2@mail.gmail.com> Date: Fri, 11 Aug 2006 00:37:35 +0200 From: "Jesper Juhl" To: "Grant Coady" Subject: Re: 2.6.17.8 - do_vfs_lock: VFS is out of sync with lock manager! Cc: "Linux Kernel Mailing List" , "Trond Myklebust" , nfs@lists.sourceforge.net In-Reply-To: <9a8748490608090107j6ce7bc2cr2b74cc13b9541f39@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9a8748490608080739w2e14e5ceg44a7bf0a3b475704@mail.gmail.com> <9a8748490608090107j6ce7bc2cr2b74cc13b9541f39@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2450 Lines: 54 On 09/08/06, Jesper Juhl wrote: > On 09/08/06, Grant Coady wrote: > > On Tue, 8 Aug 2006 16:39:54 +0200, "Jesper Juhl" 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 ;) -- Jesper Juhl 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 - 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/