Problem when try mounting a vgXXXX

[Bruno Rebelo Lobato]

When a reboot my system some mount points don become up then i try run a mount -a and receive de following erros :

vxfs mount: /dev/vgRAID2/lvoldata3 is corrupted. needs checking
vxfs mount: /dev/vgRAID2/lvolarchive is corrupted. needs checking
mount - file system on /dev/vgRAID2/lvoldata1 has structural damage

Please help me!

Thank You !

[James A. Donovan]

Hope you have good backups, you may end up needing them...

You can try to fix the problem using the fsck command.

# fsck -F vxfs -o full -y /dev/vgRAID2/lvoldata3
# fsck -F vxfs -o full -y /dev/vgRAID2/lvolarchive
# fsck -F vxfs -o full -y /dev/vgRAID2/lvoldata1

Leave the -y out of the above commands, and you will be asked to respond yes/no to fix the corrupted filesystems.

Once the filesystems are corrected, you should be able to mount them.

[A. Clay Stephenson]

I am guessing that you ran the "reboot" command rather than the "shutdown -r" command. Avoid the reboot command because it does not run the rc scripts to cleanly unmount and shutdown subsystems.

You need to run the following command on each filesystem. (I assume these are all vxfs filesystems):

fsck -F vxfs /dev/vgRAID2/rlvoldata3

Normally you answer "y" to the questions.

You may need to do a full fsck (but this is not often required)


fsck -F vxfs -o full,nolog /dev/vgRAID2/rlvoldata3

Man fsck_vxfs for details.

[Joshua Scott]

the only times i've gotten a structural damage message was when a disk failed or was removed.

What type of disk system is the /dev/vgRAID2 volume group on?

Josh

[Sanjiv Sharma_1]

Hi Bruno,

I hope you have a data backup. First try fsck. Most of the time it helps.

Please check this document:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=317817
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=13072

hth.

[Trond Haugen]

Hopefully the fsck fixed you filesystems. But I would reccomend looking into why it happened too. As A.Clay mentioned "reboot" could be to blame. Taking a look at /etc/rc.log.old could give you some clue.

Regards,
Trond