Operating System - HP-UX
1836589 Members
1301 Online
110102 Solutions
New Discussion

ignite - Path name element too long - skipped

 
SOLVED
Go to solution
Richard Pereira_1
Regular Advisor

ignite - Path name element too long - skipped

Hi,

Im running Ignite-UX B.4.1.61 with pax PHCO_26422. I noticed a small problem with long file names during my make_net_recovery

pax: usr/local/Tivoli_r11.old/lcf/dat/2/LCFNEW/Tmw2k/Unix/data/profiles/646263697231315F5231315F31312E6D79534150204A6F6220537461747573236367697469766F6C692D726567696F6E.dmprf : Path name element too long - skipped
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete

Checked latest ignite notes, no mention, checked latest pax patch, not sure if its covered, any other work arounds?

Thanks in advance,
Richard
5 REPLIES 5
Steven E. Protter
Exalted Contributor

Re: ignite - Path name element too long - skipped

Its probably worth upgrading Ignite to the 6.x version.

This is specifically a pax error.

pax patch:

http://www1.itrc.hp.com/service/patch/patchDetail.do?BC=patch.breadcrumb.main|patch.breadcrumb.search|&patchid=PHCO_30420&context=hpux:800:11:11

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Pete Randall
Outstanding Contributor

Re: ignite - Path name element too long - skipped

Richard,

I have to question what something like that is even doing in /usr/local. Is it something that Tivoli put there during its install? The name "Tivoli_r11.old_blah_blah" indicates to me that you needn't worry about it - it sure doesn't sound like it's necessary.

As a matter of personal preference, I like to keep things out of /usr/local - they have a nasty habit of getting overlaid when you install a new version of the OS. Software applications go in /opt, homegrown applications go in there own, non-vg00 file system.


Pete

Pete
Stanimir
Trusted Contributor

Re: ignite - Path name element too long - skipped


I suppose you could rename this specific file, if you like, before doing
make_net_recovery. :)

Any way this and the other similar problems with pax /like ACL-files and so on /could be solved by making tar.gz of these files or dirs before doing make_not_recovery. When you need to recover, simply untar and unzip those tar.gz after recovering.

Regards.
Cheryl Griffin
Honored Contributor
Solution

Re: ignite - Path name element too long - skipped

Pax is telling you that filename is exceeding the maximum allowed, so it was skipped. Upgrading to the new version of Ignite will not fix this.

# cd usr/local/Tivoli_r11.old/lcf/dat/2/LCFNEW/Tmw2k/Unix/data/profiles/
# ls 646* |wc -c

The filename itself is 102 characters.

Pax can handle a longfilename of 100 characters or less.

Any warning will mean that the pax will return a non-zero exit status. Non-zero does not mean it failed.

It appears that the archive was completed successfully in spite of the warning because you see "* Creation of system archive complete".
"Downtime is a Crime."
Richard Pereira_1
Regular Advisor

Re: ignite - Path name element too long - skipped

closing thread, thanks for the help