backup problem due to /var/tmp/

[siva baskaran]

Hi All,
i facing a problem when running the ignite backup it just giving error which i pasted here, so anybody have idean on this problem

and i have found lot of files in /var/tmp folder what kind of logs in that folder can i remove these files?



# make_tape_recovery -i
* Creating local directories for configuration files and archive.

======= 11/20/06 11:43:55 IST Started make_tape_recovery. (Mon Nov 20
11:43:55 IST 2006)
@(#) Ignite-UX Revision C.6.7.79
@(#) net_recovery (opt) $Revision: 10.778 $

NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/defaults.

* Checking Versions of Ignite-UX filesets

* Creating System Configuration.
WARNING: The volume group /dev/vg00 will be only partially included in the
System Recovery Archive. This means that not all files and
directories on this volume group will be restored when the archive is
installed. This message can be suppressed using the "-P s" option for
make_tape_recovery. See make_tape_recovery(1M) for more details.

* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2006-11-20,11:43/system_cfg vg00 vg02 vg03
vg01
* 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/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

* 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

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

* /opt/ignite/lbin/make_arch_config -c
/var/opt/ignite/recovery/2006-11-20,11:43/archive_cfg -g
/var/opt/ignite/recovery/2006-11-20,11:43/flist -n 2006-11-20,11:43 -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
8519+0 records in
8518+1 records out
I/O error
ERROR: /usr/bin/dd if=/var/tmp/uxinstlf.recovery of=/dev/rmt/1mn bs=2k failed
to write LIF onto tape.
ERROR: Failed to generate LIF on tape .


======= 11/20/06 11:47:11 IST make_tape_recovery completed unsuccessfully
#

[Steven E. Protter · Accepted solution]

Shalom,

The filesystem that /var/tmp is mounted on, which is by default /var is too full.

Your Ignite backup will not succeed until you clear space on /var

Suggestions:
sam normal operations, trim the log files, they can get pretty big.

bdf /var

cd /var
du -k | sort -rn | more
# find some big files and get rid of them.

SEP

[Fabian Briseño]

Hi siva.

I faced the same problem a few days ago. And like steven said you need to free up space in /var

You could run an fbackup on /var prior to deleting files on var as a precaution

look for core files in var and probably running the cleanup command to remove some superseeded pathches while also help.

Do a man cleanup to see the options

And also like steven said run sam and cleanup some log file.

[siva baskaran]

thanks to stevan and another for very quick reply,
now i am facing some other problem now i running non iteracting mode previously i issued interactive mode. by non interactive mode it is giving error which i pasted herewith so please suggest.



# make_tape_recovery -f /dev/rmt/1mn
* Creating local directories for configuration files and archive.


thanks
siva


======= 11/20/06 12:24:55 IST Started make_tape_recovery. (Mon Nov 20
12:24:55 IST 2006)
@(#) Ignite-UX Revision C.6.7.79
@(#) net_recovery (opt) $Revision: 10.778 $

* Testing for necessary pax patch.
* Passed pax tests.
NOTE: Detected entries in the defaults file at
/var/opt/ignite/recovery/defaults.

* Checking Versions of Ignite-UX filesets

ERROR: The list_expander command failed. This could be due to a problem with
parsing /etc/fstab or /etc/mnttab file - see messages above.

======= 11/20/06 12:24:57 IST make_tape_recovery completed unsuccessfully
#

[siva baskaran]

and size very small

/dev/vg00/lvol3 2097152 319304 1764016 15% /
/dev/vg00/lvol1 511672 146000 314504 32% /stand
/dev/vg01/lvol1 10485760 19038 9812559 0% /vault_loc
/dev/vg00/lvol8 15728640 1207288 14407920 8% /var
/dev/vg00/lvol7 8388608 3149160 5198528 38% /usr
/dev/vg00/lvol4 1048576 293832 749616 28% /tmp

even i couldn't run without vg00

thanks
siva

[Fabian Briseño]

Hi siva.

This could be a problem in fstab.

if you have a lvol there that no longer exists it could be given you trouble, you couald try commenting it a re-running ignite to see if it works.

[siva baskaran]

Dear i have checked out these thing anyway let check it out
# cat /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg01/lvol1 /vault_loc vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg02/lvol1 /data1 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg03/lvol1 /data2 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg03/lvol2 /data3 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg03/lvol3 /data4 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
/dev/vg03/lvol4 /data5 vxfs rw,suid,largefiles,delaylog,datainlog 0 2
#
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 2097152 319304 1764016 15% /
/dev/vg00/lvol1 511672 146000 314504 32% /stand
/dev/vg01/lvol1 10485760 19038 9812559 0% /vault_loc
/dev/vg00/lvol8 15728640 1070848 14543328 7% /var
/dev/vg00/lvol7 8388608 3149168 5198520 38% /usr
/dev/vg00/lvol4 1048576 293832 749616 28% /tmp
/dev/vg00/lvol6 8388608 2291456 6049544 27% /opt
/dev/vg00/lvol5 1048576 16680 1023848 2% /home
/dev/vg02/lvol1 10485760 3377823 6663697 34% /data1
/dev/vg00/lvol9 10485760 4065209 6019279 40% /ora9
/dev/vg03/lvol1 4194304 4018156 165141 96% /data2
/dev/vg03/lvol2 4194304 17496 3915764 0% /data3
/dev/vg03/lvol3 4194304 17496 3915764 0% /data4
/dev/vg03/lvol4 4161536 17488 3885052 0% /data5
dv04:/var 15728640 8379424 7292000 53% /patch
#


thanks
siva

[Fabian Briseño]

Siva.

What are the file permissions for fstab and mnttab ?

Also, what does your mnttab look like, do a more mnttab and list your results here please.

mnttab is located in /etc

[Fabian Briseño]

Siva I dont see
dev/vg00/lvol9 10485760 4065209 6019279 40% /ora9

In your fstab file, please confirm if this is right, if you created this lvol manually you need to add it to fstab file.

[Bill Hassell]

The original problem was an I/O error on tape. Try a different tape after running the cleaning tape through. The second problem with the list expander often means that there is a bad filename containing control characters. To find the file(s), look at the Ignite logfile.