vxfs fsck: OLT extents conflict

[Carlos Montoro Perez]

Hello,

I was trying to install sdk, and I got the following message (swinstall log)


vxfs mount: /dev/vg01/lvol1 is corrupted. needs checking


Then I tried to run a fsck:

idcux07:/#fsck -o full /dev/vg01/lvol1
vxfs fsck: OLT extents conflict
read of primary OLT failed
vxfs fsck: OLT extent 1 has bad checksum
read of OLT copy failed
vxfs fsck: no valid OLT, cannot continue
file system check failure, aborting ...


Any idea about what is the problem? Thanks in advance.

PS: My bdf (in case it may help)

idcux07:/#bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 524288 200580 303858 40% /
/dev/vg00/lvol1 299157 43613 225628 16% /stand
/dev/vg00/lvol9 1560576 812853 725256 53% /var
/dev/vg00/lvol7 667648 265970 376632 41% /var/adm/sw/save
/dev/vg00/lvol8 1675264 1369001 288155 83% /usr
/dev/vg00/lvol6 204800 155906 45997 77% /tmp
/dev/vg00/lvol5 1536000 1320364 203542 87% /opt
/dev/vg00/lsamba 102400 21524 75879 22% /opt/samba
/dev/vg00/lvol4 262144 167055 89186 65% /home
/dev/vg00/lvgcc 512000 487770 22741 96% /opt/gnu
/dev/vg01/lvollogact
3072000 1972 2878157 0% /var/opt/OV/ServiceActivator/log

[Robert-Jan Goossens]

Hi,

Could you check your disk ?

# dd if=/dev/dsk/cxtxd0 of=/dev/null bs=1024

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=496192

Regards,
Robert-Jan

[Jeff Schussele]

Hi Carlos,

OLT is the Object Location Table & is critical to find the inode & hence the file. It's a critical part of the metadata area
I don't think there's any way to fix it other than fsdb if several fsck passes do not.
BUT, fsdb is not for the faint of heart & if you don't know exactly how to use it you can cause more damage than you fix.

I think you'll have to recreate the FS & restore - that is after you rule at that the disk isn't going bad & should be replaced.

Rgds,
Jeff

[Armin Feller · Accepted solution]

"fsck_vxfs does not search for all possible alternate super blocks" is a know bug and is documented in JAGaa53168.

To get a fix, please contact your local HP Support Center.

Regards,
Armin

[Steven E. Protter]

#!/usr/bin/sh

echo "A files system check on parameter 1 is commencing\n"
fsck -F vxfs -o full -y $1

Thats a script. It will fix the problem.

SEP

[Carlos Montoro Perez]

I executed dd copy, here is the result:

idcux07:/#dd if=/dev/dsk/c5t8d0 of=/dev/null bs=1024


8891556+0 records in
8891556+0 records out


Seems to be ok

[Steven E. Protter]

#!/usr/bin/sh

echo "A files system check on parameter 1 is commencing\n"
fsck -F vxfs -o full -y $1

Thats a script. It will fix the problem.

use HFS instead of vxfs. Your error was on the /stand filesystem which can not be vxfs.

Duh Steve.

SEP

[Robert-Jan Goossens]

Duh Steven, :-)

I have never seen a /stand outside vg00

"fsck -o full /dev/vg01/lvol1"

Regards,
Robert-Jan

[Jeff Schussele]

Hi SEP,

Got to agree with R-J...

Besides fsck would have pulled the FS-type from /etc/fstab.
I still think fsdb is the only thing he can do IF the disk is not bad.
I'd be backing it up & preparing to reload on it or it's replacement.

Cheers,
Jeff

[Carlos Montoro Perez]

well, its in the /stanf filesystem, but it is still vxfs...

idcux07:/#more /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/vg01/lvol1 /backup vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2


Tried your command, but still fails, I guess I will have to contact HP support.

Thank you all a lot for your time and advices.