Nested junction-path

Here is how my fun started - I committed to my users that they can create volumes on Clustered ONTAP by themselves by running a script which will create flexvols, junction-path etc. The plan was to create their volumes' junction-paths under a single parent junction-path mounted through an automounter and all of their volumes could be simply accessed under the parent junction-path automount. Everything went well except users cannot "cd" to their own volume under parent automount - yes they can mount their volume through hard mount and also they can cd to parent automount.Here is the example:

Existing volume: flexvol1

Existing volume junction-path: /BU/flexvol1

Existing volume automounter:  /vols/flexvol1 --> vserver:/BU/flexvol1

User volume: flexvol2

User junction-path: /BU/flexvol1/flexvol2

No automounter created assuming the user volume can be accessed through automout /vols/flexvol1/flexvol2  (bummer)

Surprising the trusted host can access even the nested path so can exclude automouter issue also. Any better way to deal with the situation?



Re: Nested junction-path

Hi Rajnish,

Is it possible there's a problem with the export policy? I was looking at kb article 2017281 to see if this might match what you're seeing. What's the error message when trying to change directory?


Re: Nested junction-path

The purpose of export policies and junction paths is to avoid/bypass the use of Automounters.

Also /BU/flexvol1 - this means that flexvol1 is a direcroty (that represent the junction) and cannot be cd'ed into.

Check‎ for details of namespaces/

Below is an excerpt from the above.

No file or directory can exist in the full path to be used for the junction, but the parent directory containing the junction must exist before the junction is created. For example, if an administrator wants to junction a flexible volume into the namespace at /x/y/z, there must be a directory or junction at /x/y but there cannot be an existing file, directory, or junction at /x/y/z.

I would suggest checking the export policies once again


Re: Nested junction-path

Thanks Bala and Nat. The issue is we are hitting a strange behavior of Linux where only image RHEL5.8 is not showing the nested paths while versions before and after 5.8 are working OK. Working with Netapp support to confirm what module changes were made in 5.8 to exhibit this behavior.