Nfs mount hangs while automounting home

Bug #962001 reported by Alex Bachmeier
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
autofs5 (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

On my Ubuntu Precise nfs clients with autofs, the mount.nfs process hangs for hours until the autofs service is restarted.
I haven't been able to get an strace from this, since it doesn't happen all the time.
I do have a kernel log trace, since sshd was being blocked which resulted in a hung task.

The nfs server is running Ubuntu Lucid. This behavior did not happen with the previous 11.04 clients.

This bug might also be related to nfs-common.

Versions:
autofs5 5.0.6-0ubuntu4
nfs-common 1:1.2.5-3ubuntu1
linux-image-generic 3.2.0.19.21

Revision history for this message
Alex Bachmeier (cebalrai) wrote :
description: updated
Revision history for this message
James Page (james-page) wrote :

Hi Alex

Are you using nis as well?

Revision history for this message
Alex Bachmeier (cebalrai) wrote :

nfs3+ heimdal Kerberos for authentication + ldap

James Page (james-page)
Changed in autofs5 (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Alex Bachmeier (cebalrai) wrote :

This bug might actually be related to nfs-common, but I'm not sure yet.
I'm debugging the situation right now.
A workaround that might be working is setting the MOUNT_WAIT variable in /etc/default/autofs

nfs debugging didn't give me anything usefel yet, I will see what I can pick up with wireshark.

After the failed mount in the syslog, the "mount.nfs" process sits there with ~16%CPU.

Revision history for this message
Alex Bachmeier (cebalrai) wrote :

I believe I have narrowed down the bug to a race condition with the 10.04 sever and its exported nfs4 shares. The nfs client tries to mount the nfs4 shares and get caught in a loop. The workaround for this is forcing nfs3 in the auto.master using:
"/home /etc/autofs/auto.home vers=3,--timeout=120"

I'm marking the bug as invalid, since this is not a problem with autofs itself.

Changed in autofs5 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.