kernel-packages team mailing list archive

[Launchpad Bug Tracker <470405@xxxxxxxxxxxxxxxxxx>]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/470405

Title:
  mount.nfs hangs when nfs server is not reachable

Status in “linux” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: nfs-common

  1. Karmic 9.10 and Jaunty 9.04

  2.1  mount.nfs -V : mount.nfs (linux nfs-utils 1.1.4) 
  2.2 nfs-common 1:1.1.4-1ubuntu1

  3. Scenario 1: when myserver is powered down the command
  mount.nfs <server:/export> <mountppoint> 
  should return with an error immediately

  4. After one minute the error is thrown:

  time mount -t nfs myserver.local:/Images /mnt/myserver
  mount.nfs: mount system call failed

  real 1m0.008s
  user 0m0.004s
  sys 0m0.004s

  Please, see also on http://sourceforge.net/projects/nfs/ :
  [...]
  commit 697e28939b7d0a3e0ffe3b6bd516213a55f5a063
  Author: Jeff Layton <jlaton@xxxxxxxxxx> Date: Mon Apr 14 09:03:13 2008 -0400
   Change
   how mount.nfs handles EACCES errors. Currently, EACCES is a non-fatal error which means the mount will be retied. This caused mounts to hang for 2mins when the client does not have permission to access the export. In a strict interpretation, the error that should be returned is EPERM, but this is not always the case. So due to the fuzzy interpretation, of EPERM and EACCES, EACCESS is now a fatal error Signed-off-by: Steve Dickson <steved@xxxxxxxxxx> 
  [...]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/470405/+subscriptions