All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Thanos Chatziathanassiou <tchatzi-nz9JlX+3IF8@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: kernel 2.6 and simulated flock() with posix locks
Date: Thu, 28 Feb 2008 17:32:49 -0500	[thread overview]
Message-ID: <20080228223249.GD30782@fieldses.org> (raw)
In-Reply-To: <47C2EFFB.40807-nz9JlX+3IF8@public.gmane.org>

On Mon, Feb 25, 2008 at 06:42:35PM +0200, Thanos Chatziathanassiou wrote:
> J. Bruce Fields wrote:
>> On Mon, Feb 25, 2008 at 03:20:29PM +0200, Thanos Chatziathanassiou wrote:
>>   
>>> Hi,
>>>
>>> I've been trying to replace kernel 2.4 in a web server mounting its Document Root via NFS with kernel 2.6 and faced a rather disturbing problem.
>>> About 1/2 hour after starting, the server would stop serving requests though it seemed fine.
>>> Earlier 2.6 kernels exhibited the ``do_vfs_lock: VFS is out of sync with lock manager!'' symptom, later (when this was changed to a dprintk()) just sat there.
>>> No apparent error apart from apache compaining ``[error] server reached MaxClients setting, consider raising the MaxClients setting'', unable to serve any requests.
>>>
>>> This issue does not surface under 2.4, where everything works as expected.
>>> I came across this  
>>> (http://blog.notreally.org/articles/2007/12/19/modifying-a-live-linux-kernel/) 
>>> where apparently they faced the same problem, but their solution 
>>> (which seemed a little crude) resulted in apache spitting ``There are 
>>> no available locks'' messages (or roughly this, translated from my 
>>> regional settings).
>>>
>>> Is there any solution to this or a way to get 2.4 behavior under 2.6 ?
>>>     
>>
>> I'm a little confused--how do you know that the problem you face is the
>> same as the one described on the blog above?  Are you re-exporting NFS
>> via Samba?
>>
>> --b.
>>   
> Indeed I am. But I am willing to convince you ;) What kind of debug info  
> would I need to collect to find out what really the problem is ?

Can you give a more detailed explanation of the symptoms?  For example,
when you say "the server would stop serving requests", are you referring
to the web server or the nfs server?  If you think the problem is that
Apache is hanging on a lock, you should be able to verify that with
strace or /proc/locks or a sysrq-T trace.

--b.

  parent reply	other threads:[~2008-02-28 22:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 13:20 kernel 2.6 and simulated flock() with posix locks Thanos Chatziathanassiou
     [not found] ` <47C2C09D.2010203-nz9JlX+3IF8@public.gmane.org>
2008-02-25 16:38   ` J. Bruce Fields
2008-02-25 16:42     ` Thanos Chatziathanassiou
     [not found]       ` <47C2EFFB.40807-nz9JlX+3IF8@public.gmane.org>
2008-02-28 22:32         ` J. Bruce Fields [this message]
2008-02-29 15:20           ` Thanos Chatziathanassiou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080228223249.GD30782@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tchatzi-nz9JlX+3IF8@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.