From: Julian Rogan (Julian.Rogan@Unilever.com)
Date: Wed Feb 04 2004 - 12:10:36 EST
Hi,
I have just done the following (after forgetting about the 128 GB limit on
filesystems)
I increased a logical volume to 160 GB and then issued the fsadm command
to increase the filesystem
I got the message:
fsadm: /etc/default/fs is used for determining the file system type
fsadm: /dev/vg01/roradbs is currently 81920000 sectors - size will be
increased
fsadm: attempt to resize /dev/vg01/roradbs failed with errno 28
The filesystem starting spewing out I/O errors and we lost access to the
applications. I tried to fsck and got the
following output:
fsck -y -o full /dev/vg01/oradbs
fsck: /etc/default/fs is used for determining the file system type
intent log marked bad in super-block
cannot perform log replay
pass0 - checking structural files
pass1 - checking inode sanity and blocks
pass2 - checking directory linkage
pass3 - checking reference counts
pass4 - checking resource maps
free block count incorrect 100755947 expected 84011499 fix? (ynq)y
free extent vector incorrect fix? (ynq)y
OK to clear log? (ynq)y
set state to CLEAN? (ynq)y
Mount still fails with filesystem corrupt.
I have managed to mount th efilsystem in readonly mode and currently
copying the data over to a new filesystem.
So finally to my question: I there a way to fix the filesystem?
regards,
Julian
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:38 EDT