DragonFlyBSD

: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

Hi guys,

Do we all agree we should switch to intr by default?

Cheers,
Antonio Huete

On Mon, 02 Jun 2014 13:19:44 +0200,
<bugtracker-admin@leaf.dragonflybsd.org> wrote:

Issue #847 has been updated by tuxillo.

Hi guys,

Do we all agree we should switch to intr by default?

I use intr on all my boxes and don't see why one wouldn't.

But there might be issues I don't know of, so more feedback is appreciated.

Sascha