On Wed, 2008-06-18 at 17:40 -0700, Jim Carter wrote: > The edited patch set went on with no problems and compiled cleanly; the > module works normally.
Thanks for your perseverance with this Jim. > > > I rebuilt the daemon with these patches: > autofs-5.0.2-dns-name-lookup.patch > autofs-5.0.3-dont-fail-on-empty-master-fix-2.patch > autofs-5.0.3-mount-thread-create-cond-handling.patch > autofs-5.0.3-mount-thread-create-cond-handling-fix.patch > autofs-5.0.3-dont-abuse-ap-ghost-field.patch > autofs-5.0.3-submount-shutdown-recovery-7.patch > > At first I thought it was still failing as before, but on looking more > closely at the output I see a new behavior which is much better than > failing. After 35 minutes and about 1200 mount/unmount cycles, it took > over 25 seconds to mount (and readdir) 12 filesystems distributed over > 6 machines. 2 minutes later these all had been mounted, and 4 > filesystems on 2 other machines were stuck. 7 minutes later these were > finished and 5 filesystems on one machine were stuck. This continued > (12 groups total) until I stopped the test 30 mins later. Syslog (debug > priority) had not a single line from autofs or NFS for the entire > period. Sorry, I'm not entirely clear on what you described here. Are you saying that there were no hangs but you observed only, what appeared to be, significant delays. I also saw this but only occasionally and only for fairly brief times. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
