Bug #847

processes getting stuck on mount point

Added by corecode over 6 years ago. Updated about 1 month ago.

Status:FeedbackStart date:
Priority:NormalDue date:
Assignee:tuxillo% Done:

0%

Category:Kernel
Target version:3.8.0

Description

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

mount_nfs01.diff Magnifier (1.17 KB) tuxillo, 02/24/2014 08:36 AM

History

#1 Updated by dillon over 6 years ago

: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

#2 Updated by tuxillo about 1 year ago

  • Description updated (diff)
  • 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

#3 Updated by tuxillo about 1 month ago

  • Description updated (diff)
  • Category set to Kernel
  • Target version set to 3.8.0

#4 Updated by tuxillo about 1 month ago

Hi,

Attached a (draft) patch for mounting NFS with 'intr' by default.

Cheers,
Antonio Huete

Also available in: Atom PDF