topic fsck Ideas in Operating System - HP-UX

fsck Ideas

brian_31 — Thu, 17 May 2007 21:42:40 GMT

I am trying to fsck a filesystem and it fails. i think i am missing something..all disk attached to this lvol are clean from ioscan

vxfs fsck: sanity check: /dev/vg01/lvol1 needs checking
mountall: cannot fsck /dev/vg01/lvol1
mountall: diagnostics from fsck
log replay in progress
pass0 - checking structural files
pass1 - checking inode sanity and blocks
file system check failure, aborting ...
no = 1074912, off = 0, len = 8192
mountall: /dev/vg01/lvol1 failed in fsck
mountall: /dev/vg01/lvol1 cannot be mounted

Please help

Thanks

brian

Re: fsck Ideas

brian_31 — Thu, 17 May 2007 21:50:53 GMT

there are 5 disks connected to this and all are clean. lvdisplay -v reports no stale extents. diskinfo is clean and so is dd. any ideas?

Thanks

brian

Re: fsck Ideas

A. Clay Stephenson — Thu, 17 May 2007 21:52:17 GMT

Try fsck -F vxfs -o full,nolog /dev/vg01/rlvol1.

Re: fsck Ideas

James R. Ferguson — Thu, 17 May 2007 21:54:06 GMT

Hi Brian:

Try:

# fsck -F vxfs -y -o full /dev/vg01/lvol1

Regards!

...JRF...

Re: fsck Ideas

Jov — Thu, 17 May 2007 21:57:51 GMT

Hi Brian,

I pretty sure fsch takes raw disks.. thus isn't 'fsck dev/vg01/rlvol1'?

Apologies for the uncertainty as I dont have access to HP-UX or have done any SA for years ;)

Jov

Re: fsck Ideas

brian_31 — Thu, 17 May 2007 23:18:38 GMT

# fsck -F vxfs -o full,nolog /dev/vg01/rlvol1
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 = 1074912, off = 0, len = 8192
file system check failure, aborting ...
#

Any Ideas before we give up on this?

Thanks

brian

Re: fsck Ideas

Asif Sharif — Thu, 17 May 2007 23:30:31 GMT

Hi Brain,

"vxfs fsck: file system had I/O error(s) on meta-data" means file system corruption as the result of a hardware defect.Run this command to just verify if your disk has any bad sectors or if your disk is completely readable.

dd if= of=/dev/null bs=2048k

Regards,
Asif Sharif

Re: fsck Ideas

A. Clay Stephenson — Thu, 17 May 2007 23:43:42 GMT

I was pretty sure that you were toast; fsck cannot correct bad disk sectors.

Re: fsck Ideas

Bill Hassell — Fri, 18 May 2007 07:09:13 GMT

> 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 a broken disk. The word I/O error means that data needed by fsck to make sense out of the directory structures is not available or corrupt. The disk is indeed toast and will have to be replaced. If you have a lot of money and the data is very important, you can contact OnTrack for data recovery services. There are several companies that specialize in data recovery but make absolutely sure they can handle HP-UX disks.

Re: fsck Ideas

A. Clay Stephenson — Fri, 18 May 2007 09:47:32 GMT

Since you did run dd and all reported well, one thing that could account for your problem is that someone reduced the size of the LVOL without first reducing the size of the filesystem --- or this is an 11.0 or earlier without the latest vxfs patches and the filesystem was reduced in size. Earlier versions of fsadm -F vxfs -b smaller_size would almost always corrupt the filesystem. Since dd worked on the LVOL, the filesystem could have block offsets that were once valid but no longer are within the boundaries of the LVOL.

Re: fsck Ideas

Steven E. Protter — Fri, 18 May 2007 09:52:33 GMT

Shalom,

fsck=file system check

Bad disks are fixed by replacing them.

SEP