> I just upgraded my primary machine and file server to 2.1.127. My
> primary machine works great, and in fact seems much faster in some ways
> (xterms in X minimize/unminimize much faster than they did).
>
> However, when running nfs on my fileserver (with the latest knfs tools),
> it hangs the maching if I enable locking by running statd on both
> machines (which is NOT documented anywhere, sigh). I mount the drive,
> use the testlk utiltity (or a program that does locking) and the
> fileserver dies.
>
> I rolled the fileserver back to 2.1.126 and there are no problems now.
> And according to testlk, locking works.
I just barely posted a report about this exact problem. There is
something that needs to be properly fixed in the lockd code. It broke
from the change in schedule(). And, yes, the failure is rather dramatic
:-).
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/