Unable to install/upgrade OPMS. Getting a XFS d_type error.
search cancel

Unable to install/upgrade OPMS. Getting a XFS d_type error.


Article ID: 142981


Updated On:


CA App Synthetic Monitor DX Application Performance Management


I am attempting to upgrade the OPMS from to

Getting the following error:

[root@apps117p install]# ./asm-opms-
Preparing to install
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Graphical installers are not supported by the VM. The console mode will be used instead...

Choose Locale...

  ->1- English
    2- Español
    3- Français
    4- Português  (Brasil)

CA App Synthetic Monitor On-premise Monitoring Station(created with InstallAnywhere)

Preparing CONSOLE Mode Installation...


Please Wait

XFS error

d_type on XFS filesystem not supported

Directory entry type (d_type) on XFS filesystem is not supported. The docker
overlay2 storage driver relies on that. For more information, see Docker
Overlay documentation


[root@apps117p install]#

Please advise


Release : 10.3 and later

Component : ASM


The default filesystem for RH7 / CentOS 7 is XFS. In older 7.X versions the filesystem was created with flag ftype=0 (d_type support - directory entry type) which is a blocker for the docker overlay2 storage engine. Even when the OS is upgraded to the latest version, the filesystem is not fixed. More information can be found here:





The 10.3 ASM installer now has a check to see if the d_type = 1. This is a Docker requirement. It is not possible to install ASM with a d_type feature disabled (dtype=0). It will fail if the file system /var is a dtype = 0


1) Completely reinstall the OS using the latest RH / CentOS 7.7 version. Make sure the root filesystem is not reused but created from scratch. No extra steps are needed - the XFS filesystem is currently created with this flag enabled by default.

2) if you have newer version of RH / CentOS 7.X upgraded from older version and do not want to rebuild the whole filesystem, just create a new volume and mount it as /var (works with current installer or /var/lib/docker (this requires the latest installer which will be published with the next hotfix):


$ mkfs.xfs -n ftype=1 /var

checksum: fbbcd95b9550a8b6d3f06b3535bf4d73

If the OPMS is completely reinstalled (option 1) with the very same host name and user selects the same location during the opms installation, the station will replace existing one and there is no need to update monitors to use the station - everything will be preserved.

If the host name is different and location the same, monitors need no change but the old OPMS (by host name) should be deleted in the ASM UI.

If the host name is different and location too, monitors must be edited to use the new OPMS and old OPMS should also be deleted in the ASM UI.

Additional Information

After creating the new mount point, you can verify by doing this: 

$ xfs_info /var

meta-data=/mount-point isize=512    agcount=4, agsize=2620928 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=10483712, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=5119, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

 See https://docs.docker.com/storage/storagedriver/overlayfs-driver/ for further details.