NFS mount hangs ls and nautilus

Bug #760744 reported by Peter Halicky
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have a NFS server on the network (Ubuntu Server 10.10 64bit) which exports several directories. I have these mounted on my 11.04 desktop (also 64bit). When I open these folders in nautilus, the window opens but then freezes. I never let it run longer than 10-20 seconds. When I open a terminal, chdir into the directory and run "ls", there's no output and I can't stop ls using Ctrl-C. It starts growing in size (several gigabytes of memory used, monitored by top), then the system starts swapping and I have to kill the process with "kill -9".

It does not happen always, but I have not found a key to trigger or un-trigger this behaviour.

This started happening after I upgraded the desktop from 10.10 to 11.04 beta.

This is how it is mounted on the desktop:
homesvr:/data/media on /data/media type nfs (rw,hard,intr,vers=4,addr=10.31.41.2,clientaddr=10.31.41.24)

And this is the export on the 10.10 server:
/data/media nexus(rw,no_subtree_check)

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-generic 2.6.38.8.22
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: peto 2640 F.... pulseaudio
 /dev/snd/pcmC0D0p: peto 2640 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff8000 irq 45'
   Mixer name : 'Analog Devices AD1989B'
   Components : 'HDA:11d4989b,10438311,00100300'
   Controls : 47
   Simple ctrls : 26
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xfe9fc000 irq 17'
   Mixer name : 'Nvidia GPU 16 HDMI/DP'
   Components : 'HDA:10de0016,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
Date: Thu Apr 14 16:19:21 2011
EcryptfsInUse: Yes
Frequency: Once a day.
HibernationDevice: RESUME=UUID=48ae6d22-a792-4cc5-8bc1-121fb3cc3047
MachineType: System manufacturer P5Q DELUXE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=3706115d-5877-4cb7-afb7-ebd3c281fd09 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.50
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to natty on 2011-04-04 (10 days ago)
WpaSupplicantLog:

dmi.bios.date: 03/25/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2005
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2005:bd03/25/2009:svnSystemmanufacturer:pnP5QDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q DELUXE
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Peter Halicky (peto-halicky) wrote :
Revision history for this message
Peter Halicky (peto-halicky) wrote :

I also tried mainline kernel 2.6.38-02063802.201103281246 from the mainline kernel ppa, same problem.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
peaguera (pe-aguera) wrote :

I have the same problem. Error message :
ls: memory exhausted

Nothing in the server log.

Revision history for this message
Michael Armida (marmida) wrote :

For me, this bug is consistently reproducible, and happens every single time I try 'ls'.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc2 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc2'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc2-precise/

Revision history for this message
Michael Armida (marmida) wrote :

I would do the upstream test, but the bug has vanished for me. I had a workaround (mounting after boot without referencing the entry in /etc/fstab), but the original bad behavior appears to have fixed itself.

Revision history for this message
penalvch (penalvch) wrote :

phjr, thank you for reporting this and helping make Ubuntu better. 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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.