i have symlinks in my home directory to a /net/anotherHost/export , so they always trigger a mount when i log in
I am using these options in auto.net
opts="-fstype=nfs,hard,intr,nodev,nosuid"
and /etc/default/autofs
TIMEOUT=3600
UMOUNT_WAIT=15
once i get this bug, i can see in pstree, automount is hung on an umount.nfs and mount.nfs commands
and then i can't shutdown my computer cleanly, the shutdown screen hangs forever after
unexporting nfs directories. even if i try and shutdown before the bug is trigged, it gets triggered at shutdown
thus, i never get to umount my root filesystems, and all that joy. i can't figure out a way to get the system back in order, after the bug is triggered.
i am seeing this crash after every timeout and umount in autofs. changed my timeout from 60 to 3600 and i still see the problem
Linux box05 2.6.38-10-server #46~lucid1-Ubuntu SMP Wed Jul 6 20:19:32 UTC 2011 x86_64 GNU/Linux
installed server- lts-backport- natty 2.6.38.10.20 2.6.38- 10-server 2.6.38-10.46~lucid1
linux-image-
linux-image-
i have symlinks in my home directory to a /net/anotherHos t/export , so they always trigger a mount when i log in
I am using these options in auto.net fstype= nfs,hard, intr,nodev, nosuid"
opts="-
and /etc/default/autofs
TIMEOUT=3600
UMOUNT_WAIT=15
once i get this bug, i can see in pstree, automount is hung on an umount.nfs and mount.nfs commands
and then i can't shutdown my computer cleanly, the shutdown screen hangs forever after
unexporting nfs directories. even if i try and shutdown before the bug is trigged, it gets triggered at shutdown
thus, i never get to umount my root filesystems, and all that joy. i can't figure out a way to get the system back in order, after the bug is triggered.