On Sat, Aug 27, 2005 at 11:34:09AM +0800, Ian Kent wrote: > The attempt to remount on umount fail has always been a contentious in my > opinion, however I`ve yet to see a situation that hasn't been caused by > something else that needs to be fixed.
I agree - remounting something that is already mounted should be a no-op in the nfs system. > I thought I asked for versions? > Can we have`em. Sorry - locally-compiled kernel 2.4.23, using autofs4 as a module. Debian packaging of autofs, 3.9.99-4.0.0pre10-1. Have unconfirmed sightings on kernel 2.6.8, autofs 4.1.3+4.1.4beta2-10. I don't think these sightings are credible. No reports since dropping the number of exports. > If neccessary looking at the code will tell if you have what's needed to > avoid this. Send me a copy of parse_sun.c from the source you are using > and I'll check. I'm using the Debian woody package. The following is from the source package after unpacking and building (which applies any patches). http://www.robsims.com/parse_sun.c I'll poke around the source some more. What I want to know is: 1) Are all the child mounts unmounted before unmounting the parent? 2) If not, were the system calls successful? 3) If the system calls failed, what were the error codes? 4) If all child mounts were in fact unmounted, why is the parent busy? I'll write back what I find, but may not have time for serious digging for the next couple of weeks. -- Rob _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
