public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Advise on: panic - Attempting to free lock with active block list
@ 2005-01-22  2:34 Stuart Sheldon
  2005-01-22 20:05 ` Trond Myklebust
  0 siblings, 1 reply; 2+ messages in thread
From: Stuart Sheldon @ 2005-01-22  2:34 UTC (permalink / raw)
  To: linux-kernel

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Just a heads up,

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,
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.

We have a duplicate system that is not SMP that has not shown any of
these problems. That might be by chance though...

Hope this info is useful,

Stu Sheldon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFB8bvRN2GRn8Iq8wYRAmLVAJ0dp1Zk/5KpraG1saWUCNoMD17IogCgmyPr
kOHIUD5g5EqNl+JCYzWuUc0=
=1Wji
-----END PGP SIGNATURE-----

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Advise on: panic - Attempting to free lock with active block list
  2005-01-22  2:34 Advise on: panic - Attempting to free lock with active block list Stuart Sheldon
@ 2005-01-22 20:05 ` Trond Myklebust
  0 siblings, 0 replies; 2+ messages in thread
From: Trond Myklebust @ 2005-01-22 20:05 UTC (permalink / raw)
  To: Stuart Sheldon; +Cc: linux-kernel

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>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-01-22 20:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-22  2:34 Advise on: panic - Attempting to free lock with active block list Stuart Sheldon
2005-01-22 20:05 ` Trond Myklebust

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox