[MooseFS-Users] Chromium on MooseFS filesystem

[Wilson, S. M <st...@pu...>]

Hi,


The newer versions of Chromium have issues when its user configuration/profile directory is located on a MooseFS filesystem.  This may be a Chromium bug but I thought I'd mention it on this list so that other users are aware of it.  I've only tested versions 55 and 58 of Chromium.  The issues appeared sometime after version 55 since that version seems to run fine while version 58 demonstrates the problems.


Running Chromium v58 on a filesystem using mfsmount 3.0.86 doesn't work at all; it crashes at startup with this error (plus a stack trace):

    Received signal 7 BUS_ADRERR 7f6410e12000


Chromium v58 won't crash on later versions of mfsmount (3.0.88, 3.0.90, 3.0.92) but it is very sluggish at times.  Version 55 of Chromium, on the other hand, seems to work fine on all mfsmount versions without crashing or sluggish behavior.


If I mount the filesystem using "mfscachemode=DIRECT" then I'm able to run Chromium v58 on a filesystem using mfsmount 3.0.86 without crashing.  And there is no apparent sluggishness.


This testing is done on workstations running Ubuntu 16.04 and servers (chunkservers and master) running MooseFS 3.0.90.


Regards,

Steve