make_tape_recovery failed for absense of some files

[Virender_1]

this was there in the log file


* Archiving contents of nmserver via tar image to local device/dev/rmt/0m
n.
* 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

WARNING: There was a problem with the list of files/directories to archive.
Input: /var/opt/ignite/recovery/2009-12-30,21:33/flist
The following line(s) had too few/incorrect entries in each of them.
Problem lines:
line: 5 Sent 100600 1123655336 242 8
WARNING: There was a problem with the list of files/directories to archive.
Input: /var/opt/ignite/recovery/2009-12-30,21:33/flist
The following line(s) had too few/incorrect entries in each of them.
Problem lines:
line: 5 Sent 100600 1123655336 242 8
ERROR: The make_sys_image command failed. The system recovery archive will
not be created.


======= 12/30/09 22:13:44 IST make_tape_recovery completed unsuccessfully

Is this going to be useful recovery option or should I create another image. How can I make sure this error does not reappear.

Please advice

[Dennis Handly]

>Is this going to be useful recovery option

Not with that error message.

>How can I make sure this error does not reappear?

I assume you don't have to worry about make_sys_image.log since these files were removed while making the backup.

You need to look at the line 5 in:
/var/opt/ignite/recovery/2009-12-30,21:33/flist

Perhaps comparing this to nearby lines will give you a clue? Do you have filename with spaces, etc.?

[Michael Steele_2]

Agree with Dennis. Check Input: /var/opt/ignite/recovery/2009-12-30,21:33/flist. Are these file systems all mounted?

[Virender_1]

This is the content of line 5 of:

/var/opt/ignite/recovery/2009-12-30,21:33/flist
===============================================

14 stand/ioconfig 100666 1195816282 3128 8

[Dennis Handly]

>This is the content of line 5 of:
>14 stand/ioconfig 100666 1195816282 3128 8

It looks like I read that message wrong. You need to look for a line that has:
5 Sent 100600 1123655336 242 8

Please provide the two lines before and after that line.

[VK2COT]

Hello,

Find that file and look for any problems
(for example, unprintable characters, no
ownership, and so on):

line: 5 Sent 100600 1123655336 242 8

If that file is not needed, simply remove it.

Cheers,

VK2COT

[VK2COT]

Hello,

As a learning experience for others, let me
analyse the line in flist that is
generating the error:

line: 5 Sent 100600 1123655336 242 8

Lines in flist are made of six fields
as follows :

* Full lenght of the filename,
* Filename,
* Type of the file and access permissions
in numeric format,
* Date and time of last modification of
the file (EPOCH),
* Size of the file in bytes,
* Number of disk blocks used.

Your file "Sent" is supposed to be FIVE
characters long, but it is only
FOUR. That proves that you probably have
hidden character in its name or a directory that leads to it (white-space, unprintable character, and so on).

And by the way, your file in question was
last modified:

EPOC Time is 1123655336
Weekday : 3
DayofMth : 10
Month : 8
Year : 2005
Hour : 16
Minute : 28
Second : 56
Daylight Saving : 0
Yday : 221
10/8/2005 16:28:56 DST=0 YDAY=221

I hope that helps,

VK2COT

[Virender_1]

Hi here are the two lines above and below error line

20 SD_CDROM/swagent.log 100644 1092889615 229 8
9 sent.mail 100600 1123665419 3577 8
5 Sent 100600 1123655336 242 8
7 .mailrc 100664 1123664734 146 8
4 mbox 100664 1124255340 396 8

[Virender_1]

Guys I looked into this file it was some mail send from a previous asministrator.

I will try my luck again with the make_sys_image.

Please let me know if there are some precautions I should take while preceding with the same.

[VK2COT]

Hello,

You are perfectly safe to get rid (remove) this file. Some Mail User Agents create
this kind of files with copies of outgoing emails. Not a very worthy file.

After you remove a file (or rename it to get
rid of hidden characters), re-run your
Ignite backups. It will work.

Cheers,

VK2COT