exportfs errors on boot

[MikeL_4]

We received the following error at boot time when exportfs was issued:
exportfs error: /var/opt/ignite/clients: No such file or directory
exportfs error: /var/opt/ignite/recovery/archives/vspdbsv1: No such file or directory
exportfs error: /var/opt/ignite/recovery/archives/vspgwy1: No such file or directory
exportfs error: /var/opt/ignite/recovery/archives/vspdbr1: No such file or directory
exportfs error: /var/opt/ignite/recovery/archives/vspdbr2: No such file or directory
exportfs error: /var/opt/ignite/recovery/archives/vspdbsv2: No such file or directory
exportfs error: /var/opt/ignite/recovery/archives/vspgwy2: No such file or directory

When we noticed the problem we re-issued the exportfs -av command and everything was ok.

This happened on two different servers. All
directories that it is complaining about in rc.log are on the server.

[Zinky]

Just a thought and theory.

Did you relocate /var/opt/ignite to a different filesystem? And is that Filesystem on some kind of storage that is recognized (or mounted) late in the boot process?

[MikeL_4]

/var/opt/ignite is defined in a different volume group than vg00 for the space requirements.

[Zinky]

Then there's your explanation.

Is that different VG on some form of a SAN storage that probably is activated late in the game? I know that earlier versions of SecurePath on 11.0 systems hooked up to Compaq StorageWorks arrays (EVA/MSA/VA...) HAD this problem.

You will always have this problem when you reboot your ignite server. The fix is to fix your storage subsystem's startup routine -- which will probably mean updating some rc scripts OR upgrade to a newer version of SecurePath or whatever array communications/pathing software you use.

[MikeL_4]

Yes, the vg it resides in is on the SAN network.

It just dawned on me, the VG it is using on this server is also in a Service Guard cluster, so these directories are not available until the cluster comes up.

Stupid me, but at least it helps to talk it out I guess...

The other server is the same circumstance but it's message in rc.log is:
exportfs error: nothing to export.

Would this be the same issue ??

[V. Nyga]

Hi Mike,

I think your /etc/exports is empty at that moment ... maybe a link?

Volkmar

[Robert-Jan Goossens_1 · Accepted solution]

if there is nothing to be exported (cat /etc/exports) this is only an information message (nfs started but nothing exported).

You could add or move a start scripts to export your filesystems at the end of the boot time /sbin/rc3.d/S999exportfs.

Hope this helps
Robert-Jan

[MikeL_4]

Thanks