make_sys_image pax bug error

[Amit Mehra_1]

Hello,
I am facing problem with the make_sys_image of HP-ignite. On giving the command

make_sys_image -p -l 1 -s local /dev/rmt/0m

I get error saying:
There were files that were not successfully archived because of a pax bug. Check /tmp/pax_bug_files for the list.

And pax_bug_files states that a particular directory is greater than 100 characters.

Previously I use to get the warning of pax for that I replaced the /sbin/pax file with the patched_pax file after using the SYSCMDS to create the patched_pax file. But I still got this error. Later on I installed the patch PHCO_20388. But I still I have the pax bug error.

Does anyone know why am I getting this error? and what is solution for this.

I even want to learn more about the making a system with this make_sys_image, please let me know where do I get this information.

Thanks to the everhelping people of this forum!

Amit

[Frank Slootweg]

As far as I know, this is not a (pax) *bug*, but a (standards) *limitation*. pax(1) uses the tar(1) format which is an official (SVID2, SVID3, XPG2, XPG3) standard and hence can not be changed. I.e. make_sys_image just reports that the directory name is too long to back up.

For details on the tar format see the tar(4) ( i.e. "man 4 tar") manual page, especially the parts on "name", "linkname", and "prefix".

Just out of interest: What is the directory/file name and what software is it part of?

[Amit Mehra_1]

The directory is part of Sablime database.And directory name is attached.

It could be that this is a limitation but the patch PHCO_16877 says:

1. Pax does not handle soft/hard links properly
in ustar format if the file/link names have a length >= 100 characters.
2. Pax cannot restore soft links with a length
> 100 characters in cpio format.
3. Pax does not restore hard links in cpio format.


and I have installed this patch also.

thanks
Amit

[Amit Mehra_1]

Ooops! i forgot to attach the file!

[Frank Slootweg]

The bug is that it did not generate an *error*, i.e. it failed *silently* (See the "Defect:" description of the patch ( PHCO_16877)). That bug is fixed by the patch.

However, in my opinion, the patch introduces somewhat of another bug, because the error which now *is* generated says "exposes pax bug, directory longer than 100 chars", but, as I explained, that is *not* a *bug*, but a standards *limitation*. Sigh!

Probably the author of the error message fell in the old-boys-UNIX trap of calling something a bug, which was actually a limitation, i.e. the "BUGS" section which used to be in some UNIX manual pages.