ClearFoundation Tracker - ClearCenter
View Issue Details
0020611ClearCenterapp-clearglass - ClearGLASS Enginepublic2018-07-09 09:402018-07-09 09:43
NickH 
 
normalminoralways
confirmedopen 
7.4.0 Updates 
 
0020611: ClearGLASS installation needs to check for xfs ftype
This is a bit of a complex one and could be considered a clearos-docker issue but docker (from centos) claim compatibility with both settings for the moment (up to 1.16).

If your underlying file system is xfs then ClearGLASS does not seem to start successfully unless the partition was formatted with "-n ftype=1" if it is an xfs partition. Ext4 partitions are OK. It tries to start but the api container fails soon after startup.

ClearOS prior to 7.3 formatted xfs with ftype=0 and do not seem to be compatible. This is despite Docker claiming compatibility will be removed in 1.16 and we are at 1.13. If ftype=0 you see the following message in the message log:
Jun 7 13:42:47 server dockerd-current: time="2018-06-07T13:42:47.424497984+01:00" level=warning msg="overlay2: the backing xfs filesystem is formatted without d_type support, which leads to incorrect behavior. Reformat the filesystem with ftype=1 to enable d_type support. Running without d_type support will no longer be supported in Docker 1.16."

There is a docker reference at https://docs.docker.com/storage/storagedriver/overlayfs-driver/ [^]

ClearGLASS needs to check on installation (or start up) what the underlying file system set up is for the partition where /var/clearos/docker is located. the command xfs_info fun on the partition will give the file system type e.g. "xfs_info /dev/mapper/clearos-root"

There is no way (that I have found) of converting an xfs partition. My workaround was to bind mount a folder on a compatible partition into /var/clearos/docker.

Installations of ClearOS originating from 7.3 onwards should be OK as RedHat flipped the default of the formatting command at that point.
No tags attached.
Issue History
2018-07-09 09:40NickHNew Issue
2018-07-09 09:43user2Statusnew => confirmed

There are no notes attached to this issue.