The vxfs filesystem cannot be resized
# /etc/vx/bin/vxresize -g testdg test +10g
UX:vxfs fsadm: ERROR: V-3-20340: attempt to resize /dev/vx/rdsk/testdg/test failed with errno 16
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume test, in diskgroup testdg
The full fsck flag is set.
This can be confirmed as below
#echo "8192B.p S" | fsdb -F vxfs /dev/vx/dsk/testdg/test | grep -i clean
flags 101 mod 0 clean 3c
The actual device can be obtained from the /etc/fstab file.
The key is the flags field. In this case it is "101", which breaks down to mean: VX_FULLFSCK | VX_METAIOERR | VX_DATAIOERR per the following defines:
VX_FULLFSCK 0x0001 full fsck required
VX_LOGBAD 0x0002 log is invalid, do not do replay
VX_NOLOG 0x0004 no logging, do not do replay
VX_RESIZE 0x0008 resize in progress
VX_LOGRESET 0x0010 log reset desired
VX_UPGRADING 0x0020 upgrade in progress
VX_UQUOTACHECK 0x0040 V2 only, moved to CUT in V3
VX_GQUOTACHECK 0x0080 V2 only, moved to CUT in V3
VX_METAIOERR 0x0100 file system meta-data i/o error
VX_DATAIOERR 0x0200 file data i/o error
1. It is now known that this file system has corruption, it is a good idea to perform a full backup of your data.
Also recommended is to dump the metadata with the "metasave" utility located at ftp.veritas.com as /pub/support/metasave.tar.Z. Saving the metadata is a good idea in case there are problems with fsdb later on.
2. Unmount the file system run a full fsck with the -n option to see which inodes are marked bad
fsck -F vxfs -n /dev/vx/rdsk/testdg/test | grep "marked bad"
If there is a lot of corruption then Technical Support Team should be contacted
3. Run a full fsck this will clear the full fsck flag set on the filesystem
fsck -F vxfs -y /dev/vx/rdsk/test/testdg
4.Mount & Resize the filesystem