make_sys_image command failed error

[Richard Murden]

I am trying to perform a make_net_recovery from using our Ignite Server. I am running the Ignite Version B.4.4.30 on both the server and client. I get a make_sys_image error that really doesnt tell me much. We are running HP-UX 11.0 on both machines. Attached is the recovery.log.
Thanks,
Richard

[Wouter Jagers]

Not really any bright ideas here, since I've never used pax myself..

However, first thing that comes to mind: Do you have enough space left on the server ? pax seems to be handling archives, so I guess it can fill up filesystems quite fast.

Slim chance, but worth checking :-)

rgds
Wout

[Steven E. Protter]

I have had this exact error on this version of Ignite.

The problem was solved by removing the file pax is complaining about.

Its not critical, and its probably got some illegal characters in the name.

The ACL comment is a bug(in my opinion).

SEP

[Richard Murden]

I couldnt delete the psoftftp file because it is a file system. I tried to exclude it but no luck. Got the same error. I have 30Gb over storage. Any ideas?
Thanks,
Richard

[Jim Butler]

I have seen other ignite errors when running images with Rationals (IBM) clearcase software - specfic to a patch (arpa or nfs, don't remember which)
My solution was to uninstall the rational product during the ignite process and reinstall it.
Perhaps you have a similar third party software issue.

[Richard Murden]

The file that is complaining about is an HFS file system with an access control list (ACL). Does Ignite supposrt this? Is there a patch?

[Elmar P. Kolkman · Accepted solution]

Since ignite is using pax to create the archive and pax complains it cannot use ACL's, I would say ignite doesn't support ACL's... You could try to remove the ACL's for the duration of the ignite backup, just to check...

[Elmar P. Kolkman]

You could also do another test: make a wrapper for pax that always returns exit code 0 by moving the real executable to pax.original and put up a shell script called pax with the following contents:
#!/bin/sh
$0.original $*
exit 0

Not the neatest solution, but it should run. But you still will loose your ACL's after reinstalling with the ignite tape you try to make.