From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Stuart Sheldon <stu@actusa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Advise on: panic - Attempting to free lock with active block list
Date: Sat, 22 Jan 2005 15:05:41 -0500 [thread overview]
Message-ID: <1106424341.10006.21.camel@lade.trondhjem.org> (raw)
In-Reply-To: <41F1BBD1.8020304@actusa.net>
fr den 21.01.2005 Klokka 18:34 (-0800) skreiv Stuart Sheldon:
> I had the same panic and screen error with a 2.6.9 PIII SMP system
> acting as an NFS client. This was after downgrading from a 2.6.10 kernel
> that was panic'ing in the same way. I reverted to 2.6.8 but left the
> Server (also a PIII SMP system) running 2.6.9. This occurred during
> moderate to heavy NFS activity. The patch referenced in
> http://seclists.org/lists/linux-kernel/2005/Jan/1237.html appeared to
> resolve the panic with 2.6.10, but I was having strange things happen,
That patch is already in 2.6.11-rc2.
> like failing to release file locks when the client reboots. This is a
> production system and needs to be available for users. I am currently
> trying to piece together another smp box to test with. I will post more
> if I can duplicate the problem on demand.
Failing to release file locks when the client reboots is not an NFS
client problem: that is handled entirely by the rpc.statd daemons and
the server. What kernel are you using on the server, and which version
of nfs-utils?
Cheers,
Trond
--
Trond Myklebust <trond.myklebust@fys.uio.no>
prev parent reply other threads:[~2005-01-22 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 2:34 Stuart Sheldon
2005-01-22 20:05 ` Trond Myklebust [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=1106424341.10006.21.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=stu@actusa.net \
/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
all inboxes | Powered by JetHome®