Ian, I'm not sure I'm following your message. So if my response doesn't make since, I may have misunderstood you.
I changed the entry to -fstype=auto and it looks like the fsck didn't get called. I guess this is the mount_generic portion? So this did work. I didn't know about the auto option. My original test fix was just to have the daemon ignore the failed fsck and attempt the mount. This would work, since Linux allows multiple mounts of a file system. My proposed solution would be for the automounter to check if the file system was already mounted. If so, it would skip the fsck and just go on to the mount. Also having some option flags in the map entry to skip the fsck would be useful. Thanks, --Shane > On Fri, 28 May 2004, Ian Kent wrote: > > Had a brief look at this. > > So far all I can see is that, when using the above it uses the > mount_generic module which doesn't do an fsck and mounts the fs. > This is probably not what we want but is what happens now. > > If ext2 is specified, with appropriate changes to allow for fsck failures, > then after passing the mount fails with an already mounted message? > > Anymore thoughts. > > Ian > _______________________________________________ autofs mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/autofs
