Re: kernel BUG at fs/locks.c:1932!

[Kenny Simpson <theonetruekenny@yahoo.com>]

> Hmm... That indicates that some posix locks are somehow still managing
> to survive a close().
>=20
> How did you trigger this problem? Were you signalling the process?

I was not, but I think the tests end by killing the worker threads.
I'll run it again tomorrow.  The options were '0 0 64k 4G 20 1' - from me=
mory.
No random reads or writes, 64k block size, 4GB file, 20 seconds duration,=
 1 thread.

I did not notice this when running the test... only noticed a bunch of th=
ese later in the syslog.

-Kenny


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around=20
http://mail.yahoo.com=20


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs