Very Computer

If I have

/path/to/project/data

where 'data' is the mount point containing the data, and I what to
have

/path/to/project/data/fs1
/path/to/project/data/fs2

What we're seeing currently is that automount tries to mount the new
path first, then unmount the old.  The workaround is to run automount
twice but this seems like a bug.

Does anyone have a bug ID for this or is this the expected behavior?  

Thanks.

~F

I'm not sure I understand.  Are these separate mount points underneath
the first mount point, or are they just separate directories within
'data' that you want to have some sort of access to?

Actually showing the automount table would make it clearer for us.

Quote:> What we're seeing currently is that automount tries to mount the new
> path first, then unmount the old.  The workaround is to run automount
> twice but this seems like a bug.

What OS are you running?  This is in the automount man page for Solaris
8.

NOTES
     autofs mount points  must  not  be  hierarchically  related.
     automount does not allow an autofs mount point to be created
     within another autofs mount.

But I can't tell from your post if that's what you're trying to do or
not.

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

On Thu, 12 May 2005 22:15:29 GMT, Darren Dunham

Sorry for the muddy view.  'data' was the mount point for a qtree from
a NetApp.  Then the qtree is broken up into 2 qtrees, fs1 and fs2.
Now I try and mount these 2 qtrees under the old autofs mount point of
data at fs1 and fs2, but the issue I mentioned requires 2 runs of
automount to do it.

I'm attempting to keep the same path prefix but move the mounts 1
level down.

Hopefully this is clearer.

~F

So /data *used* to be an automount point, but I dan't tell from your
description if it still is or if you've gotten rid of it.

Is autofs still managing /data or is that simply a normal directory?
Are these direct or indirect maps?  Have you restarted the automounter?

Can you post your automount maps that relate to data and the two fs
filesystems?   Can you run 'df -k /path/to/data' to see what the system
thinks of that directory?

Quote:> I'm attempting to keep the same path prefix but move the mounts 1
> level down.

Should be easy.  Remove the references to data, restart the automounter
so data becomes a normal directory, add the fs1/fs2, create the
directories for them to mount onto and run automount.

Any messages on console or in messages about automount failures?  If so,
what?

--

Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

On Thu, 12 May 2005 23:48:07 GMT, Darren Dunham

Ok, so that's the part we're trying to avoid; a 2 step process.  We
can get the new mounts if we run it twice, but we're thinking having
to do that is a bug somehow.  Maybe not.

I can't post the specific entries but here's the logical map:

/path/to/data   -rw,noquota     filerA:/vol/vol1/data

Then we break that qtree into 2 and do:

/path/to/data/fs1   -rw,noquota filerA:/vol/vol1/data1
/path/to/data/fs1   -rw,noquota filerB:/vol/vol1/data2

data is now just a path placeholder where before it was the mount
point.

If we make the change in the map in one shot it requires automounter
to be run twice, but this jacks with our configuration management and
requires a hack.  As you mention if you make the change in 2 shots it
works, but that then leads to a long delay for both propogations.

Neither are optimal, but if that's the way it is then that's the way
it is.  It just seemed this should not be the normal behavior.

~F