topic Re: file system corrupt in Operating System - HP-UX

file system corrupt

Ian Lochray — Mon, 04 Jun 2007 10:50:57 GMT

Following an unexpected power outage, one of the file systems on my HP-UX 11.00 servers will not mount (see below). Do I have any options other than restoring my backup?
# mount /t230817
vxfs mount: /dev/vg02/lvt230817 is corrupted. needs checking
# fsck -F vxfs -y /dev/vg02/lvt230817
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
log replay in progress
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = 5259664, off = 0, len = 8192
file system check failure, aborting ...
# echo $?
1
#

Re: file system corrupt

spex — Mon, 04 Jun 2007 11:00:40 GMT

If /dev/vg02/lvt230817 corresponds to a physical disk, that disk may now be defective. Obviously, you would need to replace it. At the very least, you will have to restore from a backup.

Re: file system corrupt

Ian Lochray — Mon, 04 Jun 2007 11:14:30 GMT

Is there a simple way to tell if the disk is broken. ioscan can see it OK.
# lvdisplay /dev/vg02/lvt230817
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t10d0":
The specified path does not correspond to physical volume attached to
this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg02/lvt230817
VG Name /dev/vg02
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 22000
Current LE 2750
Allocated PE 2750
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

# ioscan -fnCdisk
lClass I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 8/4.5.0 sdisk CLAIMED DEVICE SEAGATE ST34573WC
/dev/dsk/c0t5d0 /dev/rdsk/c0t5d0
disk 1 8/4.8.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t8d0 /dev/rdsk/c0t8d0
disk 2 8/4.9.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t9d0 /dev/rdsk/c0t9d0
disk 3 8/4.10.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t10d0 /dev/rdsk/c0t10d0
disk 4 8/4.11.0 sdisk CLAIMED DEVICE SEAGATE ST39173WC
/dev/dsk/c0t11d0 /dev/rdsk/c0t11d0

Re: file system corrupt

A. Clay Stephenson — Mon, 04 Jun 2007 11:25:10 GMT

This test is rather definitive:

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

If you get an i/o error here, you can definitely rule in a bad disk.

Re: file system corrupt

Bill Hassell — Mon, 04 Jun 2007 11:54:54 GMT

fsck has told you the problem:

> vxfs fsck: file system had I/O error(s) on meta-data.
> vxfs fsck: file system had I/O error(s) on user data.

fsck cannot fix bad spots on the disk so the disk must be replaced and then reloaded from backup. fsck fixes logical errors in the directories but cannot fix any hardware problems. If this data is invaluable, contact a disk recovery company like OnTrack or DriveSavers. Make sure they know something about HP-UX. NOTE: expect to pay several thousand $$$ to recover the data.

Re: file system corrupt

Mridul Shrivastava — Mon, 04 Jun 2007 23:29:27 GMT

Execute vgdisplay -v vg02 and see if disk shows as unavailable.. you could also check lvdisplay -v dev/vg02/lvt230817 this should show the stale extents.. which means disk is bad.. It happens many time that ioscan would show the disk fine however above output will show the disk as bad.. have you tried executing "diskinfo /dev/rdsk/c0t10d0" check the output of this as well.

Re: file system corrupt

Jollyjet — Tue, 05 Jun 2007 00:54:02 GMT

Have you tried removing and refixing and check it out you if still exists the same problem log a call and get replaced of the disk if it is not under AMC or Warranty do a fresh pvcreate and create volume group and check it out.

Re: file system corrupt

Marcel Burggraeve — Tue, 05 Jun 2007 09:58:05 GMT

Check the output of your lvdisplay again, it's complaing about /dev/dsk/c0t10d0

# lvdisplay /dev/vg02/lvt230817
lvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t10d0":
The specified path does not correspond to physical volume attached to
this volume group

Re: file system corrupt

Ian Lochray — Tue, 05 Jun 2007 10:08:45 GMT

I have removed the disk from the VG, recreated the LV and restored the data.