From: Olivier Poitrey <rs@rhapsodyk.net>
To: linux-kernel@vger.kernel.org
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Herbert Poetzl <herbert@13thfloor.at>
Subject: Re: lock issues
Date: Tue, 12 Oct 2004 19:58:58 +0200 [thread overview]
Message-ID: <87is9f3jj1.fsf@ice.aspic.com> (raw)
In-Reply-To: <20041012142916.GA8513@DUMA.13thfloor.at> (Herbert Poetzl's message of "Tue, 12 Oct 2004 16:29:16 +0200")
Herbert Poetzl <herbert@13thfloor.at> writes:
> NFS v3 options should be rw,intr,tcp,nfsvers=3
> (not 100% sure)
Yeah, that's correct.
Here is the panic + trace with a vanilla kernel (no vserver patch):
Kernel panic - not syncing: Attempting to free lock with active block list
[<c011aa15>] panic+0x55/0xe0
[<c0168277>] fcntl_setlk64+0x137/0x2d0
[<c010c5ac>] restore_i387_fxsave+0xac/0xb0
[<c010c64d>] restore_i387+0x9d/0xa0
[<c0151cd9>] fget+0x49/0x60
[<c01635eb>] sys_fcntl64+0x4b/0xa0
[<c010427f>] syscall_call+0x7/0xb
The panic seems to be caused by a proftpd version 1.2.9 on a Debian
Sarge. The whole distribution is mounted over NFS and both client and
server are using the 2.6.9-rc4 kernel version.
The proftpd configuration isn't that unusual except that a directory
is mounted rbinded but it doesn't seem to be the problem because I get
the same panic without it. I can provide the proftpd configuration if
needed it.
Let me know if you need some more information.
--
Olivier Poitrey
prev parent reply other threads:[~2004-10-12 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 22:57 lock issues Herbert Poetzl
2004-10-12 0:08 ` Trond Myklebust
2004-10-12 14:29 ` Herbert Poetzl
2004-10-12 17:58 ` Olivier Poitrey [this message]
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=87is9f3jj1.fsf@ice.aspic.com \
--to=rs@rhapsodyk.net \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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