1753974 Members
7058 Online
108811 Solutions
New Discussion юеВ

Re: Ignite error!

 
Amit Manna_6
Regular Advisor

Ignite error!

HI ,
I am getting following error while doing a Ignite backup.


The input line number is 310.
The source line number is 1.
make_medialif: ERROR: Cannot tar and gzip script files; possibly insufficient disk space in /var/tmp/make_medialif19710.
ERROR: System Error, /opt/ignite/bin/make_medialif failed creating boot LIF
file.
ERROR: Failed to generate LIF on tape .


======= 03/07/06 09:09:19 GMT make_tape_recovery completed unsuccessfully



Any suggestions?

14 REPLIES 14
Shaikh Imran
Honored Contributor

Re: Ignite error!

hi,

the /var filesystem is somehow being used to
it's maximum capacity.
please check the /var filesystem.

The above error is due to insufficient space in /var filesystem.
This a failure to write /var/tmp/uxinstlf.recovery.

Regards,
I'll sleep when i am dead.
Bharat Katkar
Honored Contributor

Re: Ignite error!

HI Amit,

/var filesystem is full.

See if you have lot's of crash dumps in /var/adm/crash. If so try deleting them in case not required. Other wise try trimming log files.

Imran, after long time, Where r u man? :)

Regards,


You need to know a lot to actually know how little you know
SUDHEER M S
Advisor

Re: Ignite error!

Hi,

Please have a look at the following points.
1) As you may aware ignite creats an archive file and then writes to the tape.
Check your /var filesystem and make sure you have a min of 30-50MB.
If the fs is with less space.You can zip or del old config files "files" under the /var/opt/ignite/recovery/
#find /var -xdev -size +100000 -exec ll {} \; to find out the files.
#check /var/adm/crash for any crash files (If same fs).
2) You may try a dd
#dd if=/etc/issue of=/dev/rmt/0mn and try write to the tape.
3) LIF write problem may cause because of media problem too. Try changing too.

Regards,
MS
Mark Greene_1
Honored Contributor

Re: Ignite error!

As stated above, /var is full. Look in directories /var/tmp, /var/spool/cron/tmp, /var/spool/locks, /var/spool/mqueue, and /var/spool/sw for large file or a very large amount of old files.

Also check in /var/adm/syslog (or where ever syslog.conf has your system messages going) to see how large the syslog is and if it's rotating properly, and look in /var/adm/cron to see how large the cron log is getting too.

mark
the future will be a lot like now, only later
Amit Manna_6
Regular Advisor

Re: Ignite error!

HI,

dd if=/etc/issue of=/dev/rmt/0mn
2+1 records in
2+1 records out

Also there is more than 100mb space free in /var.

So not sure why its failing
SUDHEER M S
Advisor

Re: Ignite error!

Good, Fire ignite again and see the status.
If fails can you please upload the

/var/opt/ignite/recovery/latest/recovery.log

Regards
MS
Mark Greene_1
Honored Contributor

Re: Ignite error!

>Also there is more than 100mb space free in /var.

That may not be enough. Are there residual file in /var/tmp/ign_configure or in /var/opt/ignite/recovery/[date] where [date] is from a previous ignite? The flist file in that directory can be very large, depending on the number of files being backed-up. The files /var/opt/ignite/recovery/makerec.last and arch.include can also be several MB each.

mark
the future will be a lot like now, only later
Ninad_1
Honored Contributor

Re: Ignite error!

Amit,

This may be a silly suggestion - but from the discussion uptill now it seems that you have been checking the free space in /var - its possible that /var/tmp is a separate filesystem and its getting full ??

Regs,
Ninad
Amit Manna_6
Regular Advisor

Re: Ignite error!

HI,
Please find the recovery log attached.