topic Re: Cannot repair FS in Operating System - HP-UX

Cannot repair FS

a8965 — Mon, 24 Oct 2005 11:19:15 GMT

On HPUX 11.00

One file system is corrupted.
After starting the "fsck" command, I have the following answer :

# fsck -F vxfs -o full,nolog /dev/vg00/lvshare
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = 262560, off = 0, len = 8192
file system check failure, aborting ...

And I still cannot do anything with the LV.

I'd like to know if there is one way to repair the FS or if I have to delete and recreate it...

Re: Cannot repair FS

CAS_2 — Mon, 24 Oct 2005 11:30:21 GMT

I suggest to run dd command to check possible I/O errors. For example

dd if=/dev/vg00/rlvshare of=/dev/null bs=2048

Re: Cannot repair FS

a8965 — Mon, 24 Oct 2005 11:47:53 GMT

I just run "dd" command and the result is ok :

131072+0 records in
131072+0 records out

Re: Cannot repair FS

Sheriff Andy — Mon, 24 Oct 2005 16:16:39 GMT

I am not so sure if you need to umount the system or not, but I am pretty sure that you need to specify the raw.

# fsck -F vxfs -o full,nolog /dev/vg00/rlvshare

Re: Cannot repair FS

a8965 — Mon, 24 Oct 2005 16:31:27 GMT

The FS is not mounted.

The "fsck" command on the raw file gives the same result :

# fsck -F vxfs -o full,nolog /dev/vg00/rlvshare
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = 262560, off = 0, len = 8192
file system check failure, aborting ...

Re: Cannot repair FS

Sheriff Andy — Mon, 24 Oct 2005 16:45:12 GMT

How does your pvdisplay (on the disks within your volumegroup) and your vgdisplay look?

Can you run a fsck -F vxfs without any options successfully?