FSCK error : file system is larger than device vxfs fsck: cannot initialize aggregate file system ch

[Divyansh]

Dear friends

I have imported a Volume group into a server.
It got imported and activated successfully.

Bu when I try to mount the filesystems, they throw an error

vxfs mount: /dev/vgp_gem_d15/lvol_app_PT_backup is corrupted. needs checking

Also, when I try to fsck it gives

root@iran:>fsck /dev/vgp_gem_d15/lvol_opt_oraias
file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...

These filesystems were mounted in the original server from I exported them...
Please help

[Robert-Jan Goossens]

Hi,

I have seen this on VeritasVolumeManager (VXVM)

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=766639

I guess you could try to translate that to LVM.

--
Check the size of the file system, using fstyp -v, calculating the number of 512 byte sectors determined by the size (in file system blocks) and bsize (bytes / file system block). Compare this to the size of the device (lvdisplay -v lvol).

The device should be smaller than the file system. The solution is to lvextend the device (partition or volume) and then the device, and then mount.

# fstyp -v /dev/vgp_gem_d15/lvol_opt_oraias

# lvdisplay -v /dev/vgp_gem_d15/lvol_opt_oraias
---

Hope this helps,
Robert-Jan

[Bill Hassell]

Somehow, the current filesystem is larger than the lvol -- just what the error message says. The only way this can happen is that someone reduced the lvol size using lvreduce. The lvreduce command has no checks for destroying filesystems so it should never be used without the latest patches, the latest version of VxFS on the filesystem and the optional product Online JFS. Otherwise, backup the data files, remove and recreate the lvol, then restore the data on the smaller lvol.

[Sandman!]

Was the lvol was reduced using the incorrect sequence of commands? Instead of first reducing the filesystem with fsadm_vxfs(1M) and then doing an lvreduce on it a step was skipped resulting in this error?

fsck the lvol on the exported server and if that's clean try the export/import process again.

~hope it helps

[siju vadakkandavida]

Please provide the following,

vgdisplay -v
lvdisplay
and bdf command output on both nodes.

[Aussan]

you'll have to re-extend it, but data won't be lost..try this

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000079994830

if the link does not open here are the steps

1. Set the appropriate size that the filesystem needs to be (where size is slightly larger by a few PE's.)
# lvextend -L size /dev/vgXX/lvolX
# extendfs /dev/vgXX/rlvolX
2. Do a full file system check
# fsck -F vxfs -o full -y /dev/vgXX/rlvolX
3. You can now mount your filesystem.
# mount /dev/vgXX/lvolXX /mount-pt