kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Christoph, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

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

-- 
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:
  Incomplete

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