On Wed, Feb 14, 2001 at 12:23:41PM +0100, Patrick Schemitz wrote:
> Hi,
>
> I'm just trying to set up autofs 4.0.0pre9 (as it comes with brand new
> SuSE 7.1) for our network and ran into a problem:
>
> What I want to do is crossmounting all the home directories of our
> Linux machines (twenty-something boxes) with a nifty wildcard map,
> via NFS. In principle this is working great, the map is a fraction
> of the old AMD map, and the mounter mounts as expected, but...
>
> When I try to "ls" a formerly unmounted directory (or "cat" a file
> on a formerly unmounted directory, it works fine... AT THE SECOND
> TRY. For the first try, it gives "No such file or directory". When
> I redo the command (from history) a second later, it works as
> expected!
>
> Interesting enough, the "cd" command works instantaniously.
>
> We're running a lot of automated jobs which write on network volumes
> and which, unfortunately, are not very forgiving about non-existant
> directories. So my question is: is there a way (an option?) to halt
> the program which demands the mount until the FS is really mounted?
That's supposed to happen, but there's some subtle synchonization stuff
going on which often gets broken by other kernel changes. The
confusing thing is that I've seen this with some servers and not others;
I don't know what the difference is.
What's your kernel version, server type, etc?
Thanks,
J
