Ignite not releasing NFS mounts

[dictum9]

After I take an image of a box, Ignite-UX seems to keep its NFS mount there. How can I make sure that Ignite releases the NFS mounts?

[Steven E. Protter · Accepted solution]

Shalom,

You need to exclude NFS mounts from any Ignite images you take.

Ignite is designed to back up the system disk, not remote NFS mounts.

SEP

[dictum9]

I did not express it clearly enough.

When you take an Ignite image, the client machine NFS-mounts the filesystem of the Ignite server. The client mounts /var/opt/ignite/clients filesystem and writes stuff to it.

The problem is that if the Ignite server gets rebooted, the client will get a hung filesystem. Its bdf will hang. Happened to me once.

[Tim Nelson]

What version of ignite are you running ?

95% of ignite problems get fixed with current releases. Current releases break the other 5% :0

[Dennis Handly]

>if the Ignite server gets rebooted, the client will get a hung filesystem.

You could have the filesystem automounted so that is typically unmounted most of the time.

[Steven E. Protter]

Shalom,

The problem is that if the Ignite server gets rebooted, the client will get a hung filesystem. Its bdf will hang. Happened to me once.

Well don't reboot the Ignite server.

If it owns the NFS share, a reboot is always going to make this happen.

Now if you relocate the NFS to say a NAS device or a share on an EMC or similar box, you can get around this.

SEP