Can't resize VxFS -- fsadm: ERROR: V-3-20013: unrecognized vxfs version number

[Gotham_Gerry]

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

[Gaurav_S]

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

[Kapalin]

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

[Gotham_Gerry]

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.

[Gotham_Gerry]

You think this is a VxVM issue, rather than a file system issue?  It looks to me like Volume Manager is working fine:

# vxassist -g datadg -U fsgen make voltest 200m layout=nolog,nostripe 

# vxprint -qg datadg voltest
v  voltest      fsgen        ENABLED  409600   -        ACTIVE   -       -
pl voltest-01   voltest      ENABLED  409600   -        ACTIVE   -       -
sd datadg05-08  voltest-01   ENABLED  409600   0        -        -       -

# vxassist -g datadg growby voltest 100m

# vxprint -qg datadg voltest
v  voltest      fsgen        ENABLED  614400   -        ACTIVE   -       -
pl voltest-01   voltest      ENABLED  614400   -        ACTIVE   -       -
sd datadg05-08  voltest-01   ENABLED  614400   0        -        -       -



 38  13890d0  3e4e0 276   1  vxdmp (VxVM 5.0MP3: DMP Driver)
 40 7be00000 209248 277   1  vxio (VxVM 5.0MP3 I/O driver)
 42 7bfe90f0    c78 278   1  vxspec (VxVM 5.0MP3 control/status driv)
195 7bbff308    cb0 279   1  vxportal (VxFS 5.0_REV-5.0MP3A25_sol port)
196 7aa00000 1d89e0  21   1  vxfs (VxFS 5.0_REV-5.0MP3A25_sol SunO)
197 7abc8000   a9e0 280   1  fdd (VxQIO 5.0_REV-5.0MP3A25_sol Qui)


VRTSvxvm  Binaries for VERITAS Volume Manager by Symantec
          (sparc) 5.0,REV=05.11.2006.17.55

VRTSvxfs  VERITAS File System
          (sparc) 5.0,REV=5.0A55_sol

   VxVM#VERITAS Volume Manager         = Enabled
   VXFS#VERITAS File System            = Enabled
   QLOG#VERITAS File System            = Enabled
   PGR#VERITAS Volume Manager          = Enabled
   VERITAS Foundation Suite            = Enabled
   SPC Lite#VERITAS SANPoint Control   = Enabled
   Storage Expert#VERITAS Volume Manager = Enabled
   Dynamic Lun Expansion               = Enabled
   Hardware assisted copy              = Enabled
   Cross-platform Data Sharing         = Enabled
   PGR                                 = Enabled
   PGR_TRAINING                        = Enabled
   RAID5SNAP                           = Enabled
   File Change Log                     = Enabled
   Cross-platform Data Sharing         = Enabled
   Extra-Big File Systems              = Enabled
   Multi-Volume Support                = Enabled
   Storage Expert                      = Enabled
   VxVM                                = Enabled
   PGR                                 = Enabled
   VXFS                                = Enabled
   QLOG                                = Enabled
   SPC Lite                            = Enabled

[g_lee]

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>

[Gotham_Gerry]

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. 

[Kapalin]

you can try uninstalling the VRTSvxfs package and install it again. This would require a reboot of server.

Kapalin

[Gaurav_S]

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