savevg failed with the following error... 1

[adelski]

I have gone into smitty savevg and tried to save the following:
Backup DEVICE or FILE [/backup2/shrg01l04_sa>
VOLUME GROUP to back up [wasovg]
List files as they are backed up? no
Generate new vg.data file? yes
Create MAP files? no
EXCLUDE files? no
EXPAND /tmp if needed? yes
Disable software packing of backup? yes
Creating information file for volume group wasovg.

Yet it brings back the following error:
/usr/bin/savevg[17]: TMPSZ = 0 * 32 * SCHED : 0403-009 The specified number is not valid for this command.

I have also tried an nfs mount but this brings back exactly the same error. The server is running 5.2, has anyone experienced anything similar before? Thanks

 

[AIX5L]

Hi

There is maybe a Problem in the Script savevg, or in your Volumegroup.

Please send the output of lsvg wasovg, and lsvg -l wasovg
What is the Error in mount remote:/remote_fs /localfs ???

 

[adelski]

Hi, Thank u for taking a look at this for me...

shrg01l04# lsvg wasovg

VOLUME GROUP: wasovg VG IDENTIFIER: 0010dfda00004c00000000f
d37228b6e
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 536 (17152 megabytes)
MAX LVs: 512 FREE PPs: 423 (13536 megabytes)
LVs: 6 USED PPs: 113 (3616 megabytes)
OPEN LVs: 5 QUORUM: 2
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per PV: 1016 MAX PVs: 128
LTG size: 128 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable


---------------------------------------------------------

shrg01l04# lsvg -l wasovg

wasovg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
wasojfs2log1 jfs2log 1 1 1 open/syncd N/A
wasowaslv jfs2 78 78 1 open/syncd /opt/waso/apps
wasolv jfs2 1 1 1 open/syncd /opt/config/waso
loglv01 jfslog 1 1 1 open/syncd N/A
lv00 jfs 0 0 0 closed/syncd N/A
lv01 jfs 32 32 1 open/syncd /usr/opt/db2_08_01


The error when mounting the filesystem, is exactly the same as when trying to backup via smitty.

 

[RodKnowlton]

If it said /usr/bin/savevg[17] in the error, there's something wrong with the /usr/bin/savevg script. Scripts provided by IBM, like /usr/bin/mksysb (which savevg is a link to), have well over 17 lines of preliminary comments.

Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L

 

[adelski]

Thank you AIX5L and Rod Knowlton....unfortunately when comparing the savevg script with another box (which the backup was successful on), it appears that there is no difference in the script contents.

 

[comtec17]

Where is the /backup2 device that you are trying to save to? Post the output of this filesystem or VG it belongs to.

 

[RodKnowlton]

Please post the output of the following command.

awk '( NR > 10 && NR < 20)' /usr/bin/savevg



Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L

 

[adelski]

Hi Rod,

Here is the output you requested:

# IBM_PROLOG_END_TAG
# @(#)78 1.21.10.1 src/bos/usr/bin/mksysb/mksysb.sh, cmdbsys, bos52B, b2
003_34A8 8/15/03 11:52:29
#
# COMPONENT_NAME: (CMDBSYS)

 

[adelski]

Hi Comtec17,

I am trying to back up the application vg (wasovg) to the /backup2 filesystem.

 

[RodKnowlton]

Working from a shell prompt, you can create a logged savevg attempt that might yield more clues. In my example, I show input in bold and system output in regular font:

/# [b]/usr/bin/script savevg_debug.txt[/b]
Script started, file is savevg_debug.txt
/# [b]/bin/ksh -x -c "/usr/bin/savevg -f/backup2/backupfile -i  -X -p wasovg"[/b]
[COLOR=red]{
lots of ouput here, including all commands executed by savevg
.
.
.
Then it fails, presumably
}[/color]
/# [b]exit[/b]
Script done, file is savevg_debug.txt
/#

You can then examine savevg_debug.txt for clues to what's going wrong. Be sure not to miss that "exit" at the end, otherwise you'll be logging your examination to the file that you're examining. That way lies madness.

If it's not too long, you could post it here, too.

Rod Knowlton
IBM Certified Advanced Technical Expert pSeries and AIX 5L