1759755 Members
3508 Online
108888 Solutions
New Discussion юеВ

fsck problems -----

 
SOLVED
Go to solution
dictum9
Super Advisor

fsck problems -----

I had a machine crash after which a vg00 filesystem did not come up. When I tried to mount it, it said to run fsck. But fsck is giving me problems:

----------------------------------------------------------------------------------


# fsck -F vxfs /dev/vg00/rlvol10
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...
#
19 REPLIES 19
Jonathan Fife
Honored Contributor
Solution

Re: fsck problems -----

Did the machine crash after an lvreduce but before the filesystem was reduced?
Decay is inherent in all compounded things. Strive on with diligence
Steven E. Protter
Exalted Contributor

Re: fsck problems -----

Shalom,

fsck -F vxfs -o full -y /dev/vg00/rlvol10

If this does not help its pretty hopeless.

You may need to run newfs which will wipe out all the data.

You of course have a good backup ready.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
IT_2007
Honored Contributor

Re: fsck problems -----

use with -o option

fsck -F vxfs -o largefiles /dev/vg00/rlvol9

spex
Honored Contributor

Re: fsck problems -----

etc,

Unfortunately, you'll have to restore vg00 from a backup.

PCS
IT_2007
Honored Contributor

Re: fsck problems -----

If something changed in the filesystem, you may not able to recover it. you may have to recreate it with newfs command.
Pupil_1
Trusted Contributor

Re: fsck problems -----

looks like ignite or backup is the last go.
There is always something new to learn everyday !!
V.Manoharan
Valued Contributor

Re: fsck problems -----

try
fsck -F vxfs -o full -y /dev/vg00/rlvol10
if doesn't work go for ignite restore.

Jaime Bolanos Rojas.
Honored Contributor

Re: fsck problems -----

Etc,

Use Steven's syntax or IT's, also you might want to add the -m option to see what returns:

http://docs.hp.com/en/B2355-60105/fsck.1M.html

"-m Perform a sanity check only. fsck will return 0 if the file system is suitable for mounting. If the file system needs additional checking, the return code is 32. If the file system is mounted, the return code is 33. Error codes larger than 33 indicate that the file system is badly damaged."

Regards,

Jaime.
Work hard when the need comes out.
A. Clay Stephenson
Acclaimed Contributor

Re: fsck problems -----

vg00/lvol10 is not a standard LVOL. You should be able to bring the machine up in single user mode and recreate the filesystem via newfs and then restore from backup.

An easier method is to bring the box up in single-user mode, mount /var and /usr and then vi /etc/fstab. I would comment the entry out of /etc/fstab and allow the box to then come up in normal multi-user mode.
You can then recreate the filesystem and restore it at leisure.

This really looks like you broke one of the system setup rules and are using vg00 for purposes other than solely for the OS.
If it ain't broke, I can fix that.