cancel
Showing results for 
Search instead for 
Did you mean: 

Ignite-UX tar errors.

 
SOLVED
Go to solution
Highlighted
Kevin Boatright
Occasional Advisor

Ignite-UX tar errors.

I"m having an issue with a make_tape_recovery on HPUX 11.11. Ignite was working and then stopped.
I originally had 7.7.89 loaded. I have attempted to reinstall ignite and downgraded to an earlier version.


* Creating local directories for configuration files and archive.

======= 01/29/09 09:36:12 EST Started /opt/ignite/bin/make_tape_recovery.
(Thu Jan 29 09:36:12 EST 2009)
@(#)Ignite-UX Revision C.7.7.98
@(#)ignite/net_recovery (opt) Revision:
/branches/IUX_RA0809/ignite/src@75250 Last Modified: 2008-08-25
11:39:14 -0600 (Mon, 25 Aug 2008)

* Testing for necessary pax patch.
* Recovery Archive Description = /dev/rmt/0mn

* Recovery Archive Location = /dev/rmt/0mn

* Number of Archives to Save = 2

* Pax type = tar


In? dsk/vg name minor# Associated disks/mountpoints
2 v /dev/vg00 0x00 /dev/dsk/c2t1d0 /dev/dsk/c2t0d0
/dev/vg00/lvol1 /stand 2
/dev/vg00/lvol2
/dev/vg00/lvol3 / 2
/dev/vg00/lvol4 /tmp 2
/dev/vg00/lvol6 /opt 2
/dev/vg00/lvol7 /usr 2
/dev/vg00/lvol8 /var 2
0 v /dev/vg01 0x01 /dev/dsk/c4t0d1 /dev/dsk/c6t0d1 /dev/dsk/c8t0d1 /dev/dsk/c10t0d1 /dev/dsk/c4t0d2 /dev/dsk/c6t0d2 /dev/dsk/c8t0d2 /dev/dsk/c10t0d2
/dev/vg01/lvol9 /home 0
/dev/vg01/lvol10 /home/emstat 0
0 v /dev/vg02 0x02 /dev/dsk/c4t0d5 /dev/dsk/c6t0d5 /dev/dsk/c8t0d5 /dev/dsk/c10t0d5
/dev/vg02/lvol11 /usr/local 0
/dev/vg02/lvphys /home/phys 0
/dev/vg02/lvconfig /home/config 0
0 v /dev/vg03 0x03 /dev/dsk/c4t0d3 /dev/dsk/c6t0d3 /dev/dsk/c8t0d3 /dev/dsk/c10t0d3 /dev/dsk/c4t0d4 /dev/dsk/c6t0d4 /dev/dsk/c8t0d4 /dev/dsk/c10t0d4
/dev/vg03/lvol12 /or_dump 0
/dev/vg03/lvtables /home/oracle/oradata/PR/tables 0
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2009-01-29,09:36/system_cfg vg00
* Backing Up Volume Group /dev/vg00
* /usr/sbin/vgcfgbackup /dev/vg00
* Creating Map Files for Volume Group /dev/vg00
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

* Backing Up Volume Group /dev/vg01
* /usr/sbin/vgcfgbackup /dev/vg01
* Creating Map Files for Volume Group /dev/vg01
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg01.mapfile /dev/vg01

* Backing Up Volume Group /dev/vg02
* /usr/sbin/vgcfgbackup /dev/vg02
* Creating Map Files for Volume Group /dev/vg02
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg02.mapfile /dev/vg02

* Backing Up Volume Group /dev/vg03
* /usr/sbin/vgcfgbackup /dev/vg03
* Creating Map Files for Volume Group /dev/vg03
* /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg03.mapfile /dev/vg03

* Creating Control Configuration.
* Creating Archive File List
* Creating Archive Configuration

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2009-01-29,09:36/archive_cfg -g
/var/opt/ignite/recovery/2009-01-29,09:36/flist -n 2009-01-29,09:36 -r
pa -b 64 -d /dev/rmt/0mn -t 1 -i 1 -m t
* Saving the information about archive to
/var/opt/ignite/recovery/previews
* Creating The Tape Archive
* Checking configuration file for Syntax
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
make_medialif: ERROR: Cannot tar and gzip script files; possibly insufficient disk space in /var/tmp/make_medialif6965.

======= 01/29/09 09:36:48 EST make_tape_recovery completed unsuccessfully

I did not find any files labeled - or 20
There is 5GB of free space in /var.

I was able to tar the filesystems directly to tape without any issue.

I did find this other thread that had the same issue but didn't see a resolution.

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1233322172759+28353475&threadId=1171617


Any ideas?

Thanks,
Kevin
26 REPLIES 26
Highlighted
Michael Mike Reaser
Valued Contributor

Re: Ignite-UX tar errors.

Somewhere on your system you have a file whose name is of the form

[string-of-characters][:space:]20[:space:][string-of-characters]

IOW, you have a file, somewhere, that has the string " 20 " buried within its name.

I ran into something similar with Ignite several years ago, where Oracle was using Unix-unsociable names eleventeen-gazillion levels deep within their directory structures. After having the DBA either rename 'em or remove 'em (I just don't remember which), tar was happy as a clam.
There's no place like 127.0.0.1

HP-Server-Literate since 1979
Highlighted
Avinash20
Honored Contributor

Re: Ignite-UX tar errors.

You could find the unprintable character via ls -b
"Light travels faster than sound. That's why some people appear bright until you hear them speak."
Highlighted
Steven Schweda
Honored Contributor

Re: Ignite-UX tar errors.

> I did find this other thread [...]

My thoughts are unchanged from back then. I
still find it hard (bordering on impossible)
to believe that any file names are causing
this problem, but if someone can actually
_demonstrate_ a "tar" failure caused by goofy
file names (in the file system, not on the
"tar" command line), instead of merely
conjecturing with no evidence, then I'd be
willing to reconsider.

> [...]
> tar: Cannot add file -: No such file or directory
> [...]

Clearly "tar" is unhappy, but I can't see
the actual "tar" command line, so I can only
guess what bad things might be there. My
_guess_ is that there are some misplaced
options which are being interpreted as file
names, but the weakness of my psychic powers
means that it's only a guess. Who made the
bad command line, and how/why, remain
mysteries.

> [...] but didn't see a resolution.

If you do puzzle it out, be sure to explain.
Highlighted
Kevin Boatright
Occasional Advisor

Re: Ignite-UX tar errors.

Mike, Oracle was installed on this box. Our vendor has been copying files from one box to another. No issues running ignite on the other box. It's running version 5.4.50.

I could not find any files with 20 in between spaces.

I was able to preform:
tar xvf /dev/rmt/0mn on /sbin /dev /stand /usr and /etc without any issues.

I also try using make_tape_recovery -m cpio and still receive the same tar error.

I guess I could try and find Ignite 5.4.50 and install that on the box.
Highlighted
Bill Hassell
Honored Contributor

Re: Ignite-UX tar errors.

> tar: Cannot add file -: No such file or directory
> tar: Cannot add file 20: No such file or directory

As mentioned, these are bad filenames. Ignite/UX (list_expander) and tar check every filename to be saved. The first is a very common error: The file is just a dash (-), or it is a dash surrounded by non-printing characters. (You can create a file with a dash like this: touch /tmp/-

The second is similar. It can be a file with a 2 followed by 0 but not necessarily together, for example, ESC 2 9 backspace 0 ESC or something similar.

In both cases, you will have to look carefully. You will have to escape the "-" as you search for it, something like this:

find / -name '*-*' -exec ls -dlb {} \;

Note that this will find any file with a dash somewhere. Remove the dash file with a a full path (ie, rm -i /tmp/*-*) Try a similar command for the 2..0 file:

find / -name '*2*0*' -exec ls -dlb {} \;


Bill Hassell, sysadmin
Highlighted
sujit kumar singh
Honored Contributor

Re: Ignite-UX tar errors.

hi

also can have a look in addition to what Bill has said at the content of the following:


/var/opt/ignite/recovery/2009-01-29,09:36/flist

regards
Sujit
Highlighted
Steven Schweda
Honored Contributor

Re: Ignite-UX tar errors.

> As mentioned, these are bad filenames.

Define "bad filename". Perhaps my VMS
experience has biased me, but is HP-UX so
lame that the
official system backup procedure can't cope
with _any_ legal file name? Really??? If
VMS had a problem like that, there'd be a mob
on the move with torches and pitchforks.

Am I the only one in the universe who finds
this explanation hard to credit?
Highlighted
Steven Schweda
Honored Contributor

Re: Ignite-UX tar errors.

And I know that I'm a bit slow, but can
someone explain why the thing says:

* Testing for necessary pax patch.

and then apparently uses "tar" instead of
"pax":

tar: Cannot add file -: No such file or directory

????

Given the limitations of the typical lame-old
"tar" program (file name length, file size,
who-knows-what-else), shouldn't it _be_ using
"pax", and not "tar"?

What obvious thing am I missing this time?
Highlighted
Patrick Wallek
Honored Contributor

Re: Ignite-UX tar errors.

pax can write output in either cpio format or tar format. The default is to write out in tar format. So as a result you have many of the same limitations as if you were to use the regular tar command.

If you happen to look at a process listing while a make_tape_recovery is being created then you would see that m_t_r does in fact use pax to create the tape.