1748021 Members
5071 Online
108757 Solutions
New Discussion юеВ

Re: ignite

 
SOLVED
Go to solution
Pete Randall
Outstanding Contributor

Re: ignite

I have to wonder if that isn't an unprintable character. The file or the whole directory was obviously transferred from a PC, thus d: designation and the back slashes in the name.

I think I would try to rename it:

mv home/jhegidus/d:*emp\ditrans\TE1.DAT home/jhegidus/d:Temp\ditrans\TE1.DAT


Pete

Pete
Ron Irving
Trusted Contributor

Re: ignite

Nope...it doesn't like the \ character.

Sigh.
Should have been an astronaut.
Dennis Handly
Acclaimed Contributor

Re: ignite

>I ran a listing of that /home directory.

Can you redo this and add "-b" to your ls?

>Pete: I think I would try to rename it:

Is a backslash a valid filename char for ignite?
And if you wanted to rename it, you would need to quote the backslashes, wildcard with "." or include in single quotes.
mv something 'd:Temp\ditrans\TE1.DAT'
Ron Irving
Trusted Contributor

Re: ignite

Ok...I ran the ls -b optoin:

006386_001.lis 022665_001.lis c:\ditrans\TE1.DAT
006670_002.lis 022665_003.lis calscss.txt
006670_003.lis 022665_005.lis calscss.txt,000
006670_007.lis 022687_001.lis calscss.txt,001
006670_008.lis 022749_001.lis d:\DC1.DAT
007205_001.lis 023932_001.lis d:\SS3.DAT
008385_001.lis 024560_001.lis d:\temp\ditrans\TE1.DAT

Not sure how it looks, but it's the last line that's offending.
Should have been an astronaut.
Pete Randall
Outstanding Contributor

Re: ignite

Duh, missed the (obvious) meaning of the back slash character.

You might consider going to the owner of this home directory and asking what this junk is. It's entirely possible that it's not needed.


Pete

Pete
Dennis Handly
Acclaimed Contributor

Re: ignite

>but it's the last line that's offending.

I would assume that all files with "\" would have the same problem.

Any reason you are including /home in your ignite backup?
You could always exclude this unmutual user's home directory.
Or tar them up and remove the individual files with the evil "\".
Ron Irving
Trusted Contributor

Re: ignite

well...I'll just exclude that in my command.

Speaking of which...how do I exclude this directory in my command?

Thanks up front!!
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: ignite

Whoa!! I think I figured it out!!

I'm holding my breath!!!!
Should have been an astronaut.
Ron Irving
Trusted Contributor

Re: ignite

Hey...!! Look at me!! I'm back!

I ran:

make_tape_recovery -v -x inc_entire=vg00 -x exclude=/home/jhegidus -a /dev/rmt/0mn

Same error:

43470+1 records in
43470+1 records out
* Complete writing boot LIF onto tape.
* /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/0mn -t n -s
local -n 2010-01-05,13:31 -m t -w
/var/opt/ignite/recovery/2010-01-05,13:31/recovery.log -u -R -g
/var/opt/ignite/recovery/2010-01-05,13:31/flist -a 3101960

* Preparing to create a system archive

* Archiving contents of lims via tar image to local device/dev/rmt/0mn.
pax: home/jhegidus/d: emp\ditrans\TE1.DAT : No such file or directory
WARNING: The pax command returned a non-zero exit status (exit status 1)
WARNING: The pax command returned a non-zero exit status (exit status 1)
* Creation of system archive complete
NOTE: The following files are in the list of files that were on the
system, but they are no longer present. These files are not
included in the back-up:
/var/tmp/ign_configure/make_sys_image.log

ERROR: The make_sys_image command failed. The system recovery archive will
not be created.


======= 01/05/10 14:10:57 EST make_tape_recovery completed unsuccessfully


I'm thinking it's looking for the make_sys_image.log, which doesn't exist in the /var/tmp/ign_configure directory.

Now what?
Should have been an astronaut.
Dennis Handly
Acclaimed Contributor

Re: ignite

>Same error:

Right. Is /home or /home/jhegidus a symlink?
Have you tried removing/renaming/archiving those evil files?

>I'm thinking it's looking for the make_sys_image.log

The NOTE said the file was there at the start but later removed. I.e. ignore it.