Ignite-UX tar errors.

[Kevin Boatright]

I found an old version of Ignite. Version B.5.4.50. Loaded that after removing 7.7.98.

I received the same error but it actually created the Ignite tape.

I'll try restoring to another box.

* Creating The Tape Archive
tar: Cannot add file -: No such file or directory
tar: Cannot add file 20: No such file or directory
tar: Error exit delayed from previous errors
Adding /opt/ignite/Version file to LIF.
46382+0 records in
46382+0 records out
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2009-02-02,11:15 -m t -w
/var/opt/ignite/recovery/2009-02-02,11:15/recovery.log -u -R -g
/var/opt/ignite/recovery/2009-02-02,11:15/flist -a 1489730

* Preparing to create a system archive

* Archiving contents of emstat via tar image to local device/dev/rmt/0mn.
* Creation of system archive complete


======= 02/02/09 11:20:30 EST make_tape_recovery completed with warnings

[Steven Schweda]

> [11328] execve("/usr/bin/tar", 0x40039d40, 0x40039de8) ... [entry]
> argv[0] @ 0x4001ee60: "tar"
> argv[1] @ 0x400219d8: "-cfb"
> argv[2] @ 0x400219f8: "-"
> argv[3] @ 0x40039d68: "20"
> argv[4] @ 0x40039d78: "./opt/ignite/data/scripts/os_arch_post_l"
> argv[5] @ 0x40039db0: "./opt/ignite/data/scripts/os_arch_post_c"

At first glance, that'd seem to me to be a
legit "tar" command:
tar -cfb - 20
(With "-f -", I'd assume that it's in a
pipeline.)

"/usr/bin/tar" would seem to be pretty
explicit, too, about which "tar" to use.

Any evidence that "/usr/bin/tar" is not what
it should be? Does a simple, similar "tar"
command work? Say,
/usr/bin/tar -cfb - 20

(That should spew to the terminal. You could
redirect it to someplace instead.)

[Dennis Handly]

>Steven: that'd seem to me to be a legit "tar" command:

Yes, it seems to work fine. Not sure why they use tar when they could use pax, possibly because those files are small?

If someone illegally replaced HP's tar by GNU tar you get similar errors:
$ PATH=/usr/local/bin tar -cfb - 20 hi.c
tar: -: Cannot stat: No such file or directory
tar: 20: Cannot stat: No such file or directory

Note: Nobody in their right mind should use the above tar syntax. Better to use:
tar -cf - -b 20 hi.c

[Kevin Boatright]

I received the following when attempting to Ignite to another box:
____________________________________________
x ./etc/passwd, 332 bytes, 1 tape blocks
x ./etc/magic, 8794 bytes, 18 tape blocks
x ./etc/hosts, 486 bytes, 1 tape blocks
x ./etc/services, 10908 bytes, 22 tape blocks
x ./etc/inetsvcs.conf, 15 bytes, 1 tape blocks
x ./etc/nsswitch.conf, 382 bytes, 1 tape blocks
x ./configure3, 454656 bytes, 888 tape blocks
x ./monitor_bpr, 24576 bytes, 48 tape blocks
* Download_mini-system: Complete
* Loading_software: Begin
ERROR: Tar: blocksize = 0; broken pipe?
ERROR: File: . not found.
ERROR: Could not load scripts from the tape.
ERROR: Missing script "/opt/ignite/data/scripts/os_arch_post_c".
* Installing boot area on disk.
* Enabling swap areas.
* Backing up LVM configuration for "vg00".
* Processing the archive source (/dev/rmt/0mn).
* Wed Feb 04 08:46:08 EST 2009: Starting archive load of the source
(/dev/rmt/0mn).
* Positioning the tape (/dev/rmt/0mn).
* Archive extraction from tape is beginning. Please wait.
_____________________________________________
#which tar
/usr/bin/tar
#what /usr/bin/tar
/usr/bin/tar:
#what /sbin/tar
/sbin/tar:
tar.c $Date: 2007/05/09 22:14:45 $Revision: r11.11/7 PATCH_11.11 (PHCO)
$ Version_11.11 May 21 2007 14:14:14 $
#cp /sbin/tar /usr/bin/tar
_____________________________________________

I reran the make_tape_recovery and I didn't receive the error:
tar: Cannot add file -: No such file or directory
tar: Cannot add file 20: No such file or directory
tar: Error exit delayed from previous errors

I reinstall Ignite 7.7.98 and ran a make_tape_recovery.
_____________________________________________
* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2009-02-06,11:26/archive_cfg -g
/var/opt/ignite/recovery/2009-02-06,11:26/flist -n 2009-02-06,11:26 -r
pa -b 64 -d Recovery\ Archive -t 1 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2009-02-06,11:26 -m t -w
/var/opt/ignite/recovery/2009-02-06,11:26/recovery.log -u -R -g
/var/opt/ignite/recovery/2009-02-06,11:26/flist -a 1497290

* Preparing to create a system archive.

* Archiving contents of emstat via tar image to local device /dev/rmt/0m.
* Creation of system archive complete.

* Archive created and rewind the tape to beginning of tape.

* Cleaning up old configuration file directories

======= 02/06/09 11:32:24 EST make_tape_recovery completed with warnings

Looks like tar was the problem. Thanks for everyone's help!

Kevin

[Steven Schweda]

Thanks for the update.

> #cp /sbin/tar /usr/bin/tar

Wouldn't be my first choice as a solution,
but it's not totally crazy. (Especially
when it apparently actually helped.)

It'd be interesting to know more about the
origin of this quirk. (Like who's more
lame, make_tape_recovery or this particular
"tar" program.)

[Dennis Handly · Accepted solution]

>Steven: >> #cp /sbin/tar /usr/bin/tar
>Wouldn't be my first choice as a solution, (Especially when it apparently actually helped.)

It got rid of the foreign devil tar.

PHCO_36587 should be reinstalled to update to the latest tar patch.

[Kevin Boatright]

Thanks for everyone's help.