17.10.2012 13:52, Harald Dunkel пишет: > Hi Michael, > > On 09/25/12 07:48, Michael Tokarev wrote: >> >> Can you please take a look at what is being done during these >> 5 minutes? Do a `ps afwx' at least, and see if there are >> any `mount' commands spawned, etc. >> > > 7826 ? Ssl 0:00 /usr/sbin/automount > 8221 ? S 0:00 \_ /bin/mount -n -t nfs -s -o noatime > nfs-home:/space/home/.pc /home/.pc > 8222 ? S 0:02 \_ /sbin/mount.nfs nfs-home:/space/home/.pc > /home/.pc -s -n -o rw,noatime
Aha. Okay. This is actually what I suspected. Please try running this same command -- the first mount -- manually, mounting it to some /mnt/foo instead of /home/.pc. It should take significant amount of time too, becase, I guess, the server does not treat this mount request as good, or something like that. In other words, this is a problem of nfs server + nfs client, not automount, -- again, just guessing. Automount can't do anything except of trying to enforce some timeout, but again, it isn't really clear which timeout to enforce, since mount really can take some time - for example, when mounting some distant location etc. Maybe automount can be told to ignore some patterns like '.*' for example, I'll try to check this. > I tried to install autofs from the backports, but this > didn't work. I could not remove autofs5: > > (Reading database ... 170412 files and directories currently installed.) > Removing autofs5 ... > Stopping automount: failed. > invoke-rc.d: initscript autofs, action "stop" failed. > dpkg: error processing autofs5 (--purge): > subprocess installed pre-removal script returned error exit status 1 > configured to not write apport reports > Starting automount: /usr/sbin/automount > already running. > done. > Errors were encountered while processing: > autofs5 Oh well. This is obviously not good. Thank you for the hint. I'll take a look at this. /mjt -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
