topic Re: lvol corrupted in Operating System - HP-UX

lvol corrupted

Jose Mosquera — Wed, 05 Nov 2008 19:57:46 GMT

Hi guys,

Some hint about this issue?

#model
ia64 hp server rx2600
#uname -a
HP-UX cxqhs103 B.11.23 U ia64 1152982660 unlimited-user license

#mount -a
UX:vxfs mount: ERROR: V-3-21268: /dev/vg01/usuarios is corrupted. needs checking

#fsck -y -o full,nolog /dev/vg01/rusuarios
pass0 - checking structural files
pass1 - checking inode sanity and blocks
UX:vxfs fsck: ERROR: V-3-25432: fsck read failure devid = 0, bno = 16680, off = 0, len = 8192
file system check failure, aborting ...

fstyp -v /dev/vg01/rusuarios
vxfs
version: 6
f_bsize: 8192
f_frsize: 1024
f_blocks: 10485760
f_bfree: 4428322
f_bavail: 4151552
f_files: 1154184
f_ffree: 1107080
f_favail: 1107080
f_fsid: 1073807361
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 10
f_fsize: 10485760

#vgdisplay -v vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 4
Open LV 4
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8683
VGDA 2
PE Size (Mbytes) 4
Total PE 8681
Alloc PE 7936
Free PE 745
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg01/usuarios
LV Status available/syncd
LV Size (Mbytes) 10240
Current LE 2560
Allocated PE 2560
Used PV 1

LV Name /dev/vg01/tape
LV Status available/syncd
LV Size (Mbytes) 7168
Current LE 1792
Allocated PE 1792
Used PV 1

LV Name /dev/vg01/oradat
LV Status available/syncd
LV Size (Mbytes) 11264
Current LE 2816
Allocated PE 2816
Used PV 1

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

--- Physical volumes ---
PV Name /dev/dsk/c2t0d0
PV Status available
Total PE 8681
Free PE 745
Autoswitch On
Proactive Polling On

#diskinfo /dev/rdsk/c2t0d0
SCSI describe of /dev/rdsk/c2t0d0:
vendor: HP 36.4G
product id: ST336753LC
type: direct access
size: 35566480 Kbytes
bytes per sector: 512

#ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
==========
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s1 /dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s1 /dev/rdsk/c2t0d0s3
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c2t1d0 /dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s1 /dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s1 /dev/rdsk/c2t1d0s3

With the rest of lvols configured in vg01 we don't have issues.

Rgds.

Re: lvol corrupted

Jaime Bolanos Rojas. — Wed, 05 Nov 2008 20:20:52 GMT

Jose,

I did not believe it, but it looks like that error is fix by a patch:

PHCO_38434

Check into it for the Error:

ERROR: V-3-25432

Regards,

Jaime.

Re: lvol corrupted

Jose Mosquera — Thu, 06 Nov 2008 11:47:30 GMT

Jaime, thanks for your answer, this patch is already installed and configured in the system:

#swlist -l fileset -a state|grep PHCO_38434
# PHCO_38434
PHCO_38434.VXFS-PRG configured
PHCO_38434.VXFS-RUN configured
PHCO_38434.VXFS-RUN-PALIB configured

Rgds.

Re: lvol corrupted

Ganesan R — Thu, 06 Nov 2008 12:02:55 GMT

Hi,

I suspect the underlying disk has bad blocks on it. why don't you try dd to check the integrity of lvol/disk.

dd if=/dev/vg01/rusuarios of=/dev/null

as well as

dd if=/dev/rdsk/c2t0d0 of=/dev/null bs=1024k

Re: lvol corrupted

Trng — Fri, 07 Nov 2008 04:11:19 GMT

Hi Jos maria,

it is clearly telling that you have bad blocks in your disk .try to correct it from SCSI controller side,if it is connected to a scisi controler.

regads
skr

Re: lvol corrupted

Torsten. — Fri, 07 Nov 2008 06:32:50 GMT

Hi Jose,

can you please post the output of

# vgdisplay -v vg00
# strings /etc/lvmtab
# lvlnboot -v
# setboot

I wonder about this:

your ioscan is showing 2 disks:
/dev/dsk/c2t0d0 - the lower internal disk
/dev/dsk/c2t1d0 - the middle internal disk

Both are partitioned, that means used as boot disks. In this case, the file system is on partition 2 (s2) = /dev/dsk/c2t0d0s2

But now your vg01 is showing the same disk /dev/dsk/c2t0d0 ???

This is strange!
But hopefully the command results will clarify.