mount nfs filesystem on third system

[Shelby K]

Here is the scenario. I have an ignite-ux server which does not have enough disk space available on local disks to use as recovery archive area. I have space available on a NetApp Filer that I can use. Space from the NetApp Filer is available as as an nfs exported FS (NAS). Is it possible to somehow re-export the NFS filesystem from the ignite-ux server to the client from which make_net_recovery is run?

[Peter Nikitka]

Hi,

though replicated NFS-mounts are possible under Linux, it is not an available feature at HP-UX (at least till 11iv2).
But the solution to your request could be an appropriate automount entry, where /var/opt/ignite/... is mapped to your NetApp.

mfG Peter

[Steven E. Protter]

Shalom,

If the rights are loose enough it is theoretically possible for your Ignite server to export a filesystem its mounted on NFS.

In general though, in practice, I've not been able to do this. In order for the export to work, the HP-UX system needs full read right access.

Then you have to mount it.

Then you have to export it.

You may run into trouble when you try the export and will need to post the error message you receive.

If its possible for the Ignite client to directly mount the NAS device via NFS, this might be more easily accomplished.

All the Ignite server MUST have is the boot files. Ignite boots its clients via tftp transfer of a boot image.

SEP

[Shelby K]

Thank you for your replies. I found a work-around after reading the Ignite documentation again. There is an option to mount a third system NFS filesystem for storing the recovery archive, when running make_net_recovery (or from the Ignite GUI). For make_net_recovery use the -a option.

[Dave Olker]

Hi Shelby,

On HP-UX, and most other NFS implementations, it is not possible for an NFS client to mount a filesystem from a server and then re-export that filesystem to other clients. This is considered a security violation and the exportfs command should return an error similar to "too many levels".

One of the basic tenets of NFS security is the server decides who gets access to the filesystem. If clients were able to mount a remote filesystem and then *the client* got to decide which systems were allowed to mount it then the security model breaks down.

Regards,

Dave

[Shelby K]

Thank you for your replies. I found a work-around after reading the Ignite documentation again. There is an option to mount a third system NFS filesystem for storing the recovery archive, when running make_net_recovery (or from the Ignite GUI). For make_net_recovery use the -a option.