Can't resize VxFS -- fsadm: ERROR: V-3-20013: unrecognized vxfs version number
Updated: 21 May 2010 | 8 comments
Trying to grow a VxFS file system. I get this error:
# vxresize -g datadg vol37 +6g UX:vxfs fsadm: ERROR: V-3-20013: unrecognized vxfs version number VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume vol37, in diskgroup datadg
The file system layout version is 7, as shown below.
I have this problem on any new file system I create, and on any existing version 7 file systems. I found a version 6 file system in this disk group, and I was able to grow it.
# mkfs -F vxfs -o largefiles /dev/vx/rdsk/datadg/voltest
version 7 layout
409600 sectors, 204800 blocks of size 1024, log size 1024 blocks
largefiles supported
# /opt/VRTS/bin/fstyp -v /dev/vx/dsk/datadg/voltest |grep version
magic a501fcf5 version 7 ctime Mon Oct 26 16:47:29 2009
# vxresize -g datadg voltest +200m
VxVM vxresize ERROR V-5-1-2331 Cannot resize volume voltest (VXFS file system not mounted)
# mount -F vxfs /dev/vx/dsk/datadg/voltest /mnt
# vxresize -g datadg voltest +200m
UX:vxfs fsadm: ERROR: V-3-20013: unrecognized vxfs version number
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume voltest, in diskgroup datadg
# /opt/VRTS/bin/fstyp -v /dev/vx/dsk/datadg/vol37
vxfs
magic a501fcf5 version 7 ctime Mon Jul 06 14:37:36 2009
logstart 0 logend 0
bsize 1024 size 4194304 dsize 0 ninode 4194304 nau 0
defiextsize 0 ilbsize 0 immedlen 96 ndaddr 10
aufirst 0 emap 0 imap 0 iextop 0 istart 0
bstart 0 femap 0 fimap 0 fiextop 0 fistart 0 fbstart 0
nindir 2048 aulen 32768 auimlen 0 auemlen 8
auilen 0 aupad 0 aublocks 32768 maxtier 15
inopb 4 inopau 0 ndiripau 0 iaddrlen 8 bshift 10
inoshift 2 bmask fffffc00 boffmask 3ff checksum ef61c963
oltext1 32 oltext2 18690 oltsize 1 checksum2 0
free 3485109 ifree 0
efree 1061 4198 5511 1035 759 437 187 99 44 24 28 24 24 18 10 6 3 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 discussion Filed Under:
Comments
Hello Gerald, What is the
Hello Gerald,
What is the Volume Manager version you are using ? Also could you please paste licensing output:
# modinfo | grep -i vx
# pkginfo -l VRTSvxvm
# vxlicrep -e |more
Thanks
Gaurav
PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
You think this is a VxVM
You think this is a VxVM issue, rather than a file system issue? It looks to me like Volume Manager is working fine:
fsadm
The error you're getting from vxresize is that it cannot run fsadm as it can't recognise the version - which is why Gaurav and Kapalin suggested checking the vxvm version first to ensure there wasn't a mismatch (which you confirmed)
Does it work if you run fsadm manually to grow the filesystem component? (since you are able to grow the volume component with vxassist)
# /usr/lib/fs/vxfs/fsadm -b <newsize> <mountpoint>
Note <newsize> is the new size in sectors (ie: the total new size, not just the increment +6g)
edit: is the diskgroup an existing DG or a newly created one (ie: since you were on 5.0MP3)? would it be possible to see the following output to check the dg version?
# vxdg list <dgname>
If this post has helped you, please vote or mark as solution
Good suggestion. I thought
Good suggestion. I thought of this too and tried it. Same error. I just did a 'pkgchk' on VRTSvxfs and it got all sorts of output, so it looks like there was a problem with patching or upgrading on this server.
I think the volume manager version is below 5.0
The file system layout version 7 is from volume manager 5.0
I guess you are trying to resize on a server which has VM version below 5.0
There is no backward compatibility.
Kapalin
I said, "I have this problem
I said, "I have this problem on any new file system I create", so we know that it is not an issue of backwards compatibility, right? Both VxVM and VxFS are version 5.
Ok, so the version is fine
you can try uninstalling the VRTSvxfs package and install it again. This would require a reboot of server.
Kapalin
since pkchk is showing
since pkchk is showing errors.... reinstall & reboot would be best..... Also, you can have latest patches applied (RP2) .. which will help to avoid some more known bugs..
Gaurav
PS: If you are happy with the answer provided, please mark the post as solution. You can do so by clicking link "Mark as Solution" below the answer provided.
Would you like to reply?
Login or Register to post your comment.