[lkml]   [2000]   [Sep]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectlocking in 2.4.0-prex (was [NFS] lockdsvc: Invalid argument)
>>>>> " " == Aaron T Porter <> writes:

> Hey -- I'm running 2.4.0-test6, using knfsd serving a few
> Solaris systems. When they try to write, I'm getting "Err#91
> ERESTART" which points to lockd. Trying to restart gives
> lockdsvc: Invalid argument, which Trond seems to imply[1]
> should be irrelevant, but something is obviously
> wrong. Suggestions?

Something seems to have broken with the locking changes introduced in
the 2.4.0-prex series.

The connectathon NFS test suite now causes a 'panic()' in
fs/locks.c:locks_free_lock() when running the various parent/child
locking tests.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.036 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site