[DragonFlyBSD - Bug #847] (Feedback) processes getting stuck on mount point

["Antonio M. Huete Jimenez via Redmine" <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #847 has been updated by tuxillo.

Description updated
Status changed from New to Feedback
Assignee changed from corecode to tuxillo

Matt,

intr is not the default for NFS mounts. Do we want this yet?

Cheers,
Antonio Huete
----------------------------------------
Bug #847: processes getting stuck on mount point
http://bugs.dragonflybsd.org/issues/847

Author: corecode
Status: Feedback
Priority: Normal
Assignee: tuxillo
Category: 
Target version: 


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


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account