Messages in this thread | | | Date | Fri, 31 Aug 2007 09:50:32 +0200 | From | Matthias Schniedermeyer <> | Subject | Re: recent nfs change causes autofs regression |
| |
> > It's not very conservative to suddenly change default behavior and break > > autofs mounts. There is not even one kernel message that "_tells_ user why > > it thinks it's wrong". It just silently fails. > > No it doesn't. It reports an error code to the caller. If autofs is > failing silently, then that is a bug in autofs: mount will report the > error to the user.
Wrong(tm).
autofs AND mounting at the commandline just say: mount.nfs: /mnt is already mounted or busy
Which has an actual information value of about 1%.
In my case i moved a nfs exported directory inside another nfs-exported directory month ago and placed a symlink where the direcotry was (on the server-side). It never acured to me that that was "wrong"(tm).
Now i can only mount one of the two mounts and the other just tells "busy".
After reading this i could fix my case easyly. I just erased the "deeper" mount and symlinked the directory from the other mount.
But YOU HAVE TO KNOW THAT YOU DID SOMETHING WRONG. Just getting a "Busy" lets you staying with Question-marks flying around you head!
Bis denn
-- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |