From: Thanos Chatziathanassiou <tchatzi-nz9JlX+3IF8@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: kernel 2.6 and simulated flock() with posix locks
Date: Mon, 25 Feb 2008 15:20:29 +0200 [thread overview]
Message-ID: <47C2C09D.2010203@arx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
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 ?
Best Regards,
Thanos Chatziathanassiou
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3229 bytes --]
next reply other threads:[~2008-02-25 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 13:20 Thanos Chatziathanassiou [this message]
[not found] ` <47C2C09D.2010203-nz9JlX+3IF8@public.gmane.org>
2008-02-25 16:38 ` kernel 2.6 and simulated flock() with posix locks 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
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=47C2C09D.2010203@arx.net \
--to=tchatzi-nz9jlx+3if8@public.gmane.org \
--cc=linux-nfs@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox