On Sun, 9 May 2004, mack wrote: > I have 6 similar systems, which automount and auto-expire floppy, zipdisk, cdrom > and nfs > mounts just fine. > > Except 2 of the systems won't umount nested nfs mounts on timeout. > These nfs mounts stay mounted forever. No messages appear the logs > not even messages to indicate that automount has timed out the > mounts and is trying to umount them. > > If I umount the lower dependant nfs mounts, leaving only the top > autofs nfs mount, the top level autofs nfs mount will expire normally. > > here is a sample line from the auto.nfs file > > routera -fstype=nfs,soft / routera:/ /usr routera:/usr /src > routera:/src > > Google didn't have any answers when looking through the mailing list > with "autofs expire nested" > > The systems are near identical (cloned progressively from each other, > so there will be some differences and some machines get updated more > often, but the differences should be small). > > Comparing the kernels of a pair of machines, one of which auto expires > OK and one which doesn't, I find in the file system section > > machine that does autoexpire nested nfs mounts > > < > Kernel automounter support > <M> Kernel automounter version 4 support (also supports v3)
Yes. It loads the autofs4 module. > > machine that doesn't autoexpire nested nfs mounts > > <M> Kernel automounter support > <M> Kernel automounter version 4 support (also supports v3) > > Re-compiling the kernel/modules on the machine that doesn't work > with the .config for the machine that does work, fixes the problem. > I assume having the first line turned on kills the auto expiration > for nested nfs mounts, but I don't know why. Using autofs-4.0.0 you need to add alias autofs autofs4 to your modules.conf to ensure that autofs4 gets loaded. I wasn't aware expire didn't work with the autofs module and v4. > > I guess this is a bug report. > I reccommend using matching autofs and daemon. > I'm using kernel 2.4.26, libc-2.3.2, gcc 2.95.3, autofs-4.0.0pre10 > > I can't get the automount from autofs-4.1.2 to load on the machine which > doesn't autoexpire. automount runs and exits with no process in the ps table, > no errors in the logs. Running with -d gives a few lines in the log files > as it fires up, but no error messages. firing up the demon under strace, > looks the same in both cases, as I don't see anything after the fork(). Are you actually sending the *.debug to the log? > > autofs-4.1.2 works fine on the machine without the first module. > > Request: Can the install script not overwrite any existing /etc/auto.* > files please? You can install new ones as auto.*.NEW if you like. OK. That bugs me as well. > > Request: Can automount be loaded without going into demon mode, so that I can > watch the logs on stdout? Not at the moment. Ian _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
