Save_config not responding

[Shrikant Lavhate]

Hi all,

There are lots of thread with same topic. I have gone through all but still can't get any solution hence troubling you with this new thread.

My save_config command didnt works good. I tried to run it using set -x parameter and found that its hanging at:

+ check_vg_in_lvm vg00
+ [[ 0 -eq 0 ]]
+ process_lvm_volume_group vg00


at this line. My disk configuration is good. All LVM related commands like bdf, lvlnboot etc. responds in good way. No network mounts in system. There is no device which is tagged as NO_HW in ioscan output.

In short everything is looking fine still command got stuck at process_lvm_volume_group line.

System info:

rp7400
HPUX 11.00
Ignite-UX-11-00 C.7.2.94 (latest for hpux11.00)


Any comment???

[Shrikant Lavhate]

Yea also there are no hardware issues on system and no errors into syslogs.

[Hasan Atasoy]

is there a unconfigured disk in the system . ?

a disk without lvm information may cause this ?

look at disk by "pvdisplay ... "

Hasan.

[Shrikant Lavhate]

No all disks are configured on system.

[Shrikant Lavhate]

All disks are properly configured and listed correctly under lvmtab file.

Any other solution ?? Hasan or anybody...?

[Hasan Atasoy]

it is possible to paste "vgdisplay -v vg00"
Hasan

[Shrikant Lavhate]

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 17
Open LV 17
Max PV 16
Cur PV 4
Act PV 4
Max PE per PV 4350
VGDA 8
PE Size (Mbytes) 4
Total PE 17360
Alloc PE 15720
Free PE 1640
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 120
Current LE 30
Allocated PE 60
Used PV 2

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 256
Allocated PE 512
Used PV 2

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 400
Current LE 100
Allocated PE 200
Used PV 2

LV Name /dev/vg00/swap1
LV Status available/syncd
LV Size (Mbytes) 4000
Current LE 1000
Allocated PE 2000
Used PV 2

LV Name /dev/vg00/swap2
LV Status available/syncd
LV Size (Mbytes) 4000
Current LE 1000
Allocated PE 2000
Used PV 2

LV Name /dev/vg00/sw_lv
LV Status available/syncd
LV Size (Mbytes) 1500
Current LE 375
Allocated PE 750
Used PV 2

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 600
Current LE 150
Allocated PE 300
Used PV 2

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 900
Current LE 225
Allocated PE 450
Used PV 2

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 600
Current LE 150
Allocated PE 300
Used PV 2

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 900
Current LE 225
Allocated PE 450
Used PV 2

LV Name /dev/vg00/lvol10
LV Status available/syncd
LV Size (Mbytes) 8200
Current LE 2050
Allocated PE 2050
Used PV 1

LV Name /dev/vg00/autosys_lv
LV Status available/syncd
LV Size (Mbytes) 200
Current LE 50
Allocated PE 100
Used PV 2

LV Name /dev/vg00/lvswap
LV Status available/syncd
LV Size (Mbytes) 8000
Current LE 2000
Allocated PE 4000
Used PV 3

LV Name /dev/vg00/lvol5b
LV Status available/syncd
LV Size (Mbytes) 2000
Current LE 500
Allocated PE 1000
Used PV 3

LV Name /dev/vg00/web_lv
LV Status available/syncd
LV Size (Mbytes) 60
Current LE 15
Allocated PE 30
Used PV 2

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 1500
Current LE 375
Allocated PE 750
Used PV 2

LV Name /dev/vg00/lvswap3
LV Status available/syncd
LV Size (Mbytes) 3072
Current LE 768
Allocated PE 768
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c1t6d0
PV Status available
Total PE 4340
Free PE 0
Autoswitch On

PV Name /dev/dsk/c2t6d0
PV Status available
Total PE 4340
Free PE 287
Autoswitch On

PV Name /dev/dsk/c7t8d0
PV Status available
Total PE 4340
Free PE 350
Autoswitch On

PV Name /dev/dsk/c6t6d0
PV Status available
Total PE 4340
Free PE 1003
Autoswitch On

[Hasan Atasoy]

hi;

is there a backslash in mount points .
bdf may help us.


Hasan

[Shrikant Lavhate]

Yes it is there.

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 409600 244664 155800 61% /

[Hasan Atasoy]

hi ;

you have probably a problem in "lvdisplay -v lvnames" .
it is possible to put all "lvdisplay -v ..." to a file and upload. ?

Hasan.

[Shrikant Lavhate]

Hasan,

I already mentioned in this thread that all lvm commands are running smoothly. I chked now also and found no problem in lvdisplay of every lvol in vg00.

[Hasan Atasoy]

hi ;

did you notice any format differences in lvdisplay output ?


Hasan.

[Shane Seymour]

The line:

+ process_lvm_volume_group vg00

is a function call to a function called process_lvm_volume_group. The posix shell does not keep set -x active through a function call. You might consider placing set -x at the start of the function call and see where it stops in that function.

If save_config has stopped when it has ran the get_system_info command run save_config as follows:

# tusc -kpaEef -o (output file) \
/opt/ignite/bin/save_config vg00

Note that the output file produced will probably be quite large.

More than likely you have a disk LUN presented to the system that responds to SCSI inquiry commands but does not respond if you attempt to open a read it. Your only choice will be to unpresent the LUN.

Look for the syscall entry that never returns (may take a while but will be towards the end) and if it's a read system call track back the fd to where it was opened and get the name of the device.

Good Luck.

[Shrikant Lavhate]

Shane ,

Thanks for the reply. Your command still dont yeild any new things.. same things happening and we dont have any LUN kinda stuff on our server.

Hasan,
There are no such remarkeble odd things in lvdislpay too..!!

Any more suggestions???

[Shrikant Lavhate]

Shane,

I checked out file and got execution is stucking at this line:

[13691] lseek64(5, 8192, 0, SEEK_SET, 0) .............................................................................. = 8192
[13691] read(5, 0x7f7f1040, 8192) ..................................................................................... [entry]


any clue??

[Shane Seymour]

Track back the open system call that returns file descriptor 5 to get the name of the file that was opened that read ended up hanging on and you have your device that is causing the hang.

[Shane Seymour]

Track back the open system call that returns file descriptor 5 to get the name of the file that was opened that read ended up hanging on and you have your device that is causing the hang.

If it's a FIFO instead of a device find out what process has the other end of the fifo and what it is doing.

[Shane Seymour]

The only other advice I'd have would be if you're not sure what you're looking for open a support call.

Someone within HP will then look at the tusc trace. You may also be asked for a debug run of save_config:

# export INST_DEBUG=5
# script
# save_config ...
# exit

The file created is called typescript in the current working directory (look at the script manual page for information on how to change the name). Provide that file to HP and there is another file you should provide: /tmp/*listener.log if it contains anything.