processes getting stuck on mount point

[Matthew Dillon]

:Hey,
:
:I just experienced the infamous ``cache_lock: blocked on 0xd591d418 ""'' message.  Checking why the process got stuck revealed that the lock is actually being held by another process which is in the process of doing a lstat(2) on /mnt, a nfs mount which server went away.  The stuck process is doing the same, fwiw.
:
:So here it is not a namecache bug, but rather an artifact of nfs being stuck.  Anoying nevertheless.  Anybody have a clue how to fix that?  Yea, mount with -intr.  Why don't we do that per default?
:
:cheers
:  simon

    I actually think changing the default to 'intr' is a good idea.

						-Matt