Open ompiteam opened 10 years ago
Imported from trac issue 4767. Created by jsquyres on 2014-07-08T09:24:19, last modified: 2014-07-08T09:39:40
Trac comment by jsquyres on 2014-07-08 09:29:03:
Actually, IU has indicated that they want to keep this fuse mount. So I made the test skip fuse filesystem mounts.
Trac comment by jsquyres on 2014-07-08 09:30:49:
(In [32152]) opal_path_nfs.c test: skip fuse filesystems
Linux statfs(2) lies about the type of fuse filesystems (it reports fuse.encfs as an NFS filesystem). So just skip fuse filesystems in this test until/if we ever care to add some kind of workaround.
Refs https://svn.open-mpi.org/trac/ompi/ticket/4767
cmr=v1.8.2:reviewer=rhc
Trac comment by jsquyres on 2014-07-08 09:39:40:
If anyone wants to fix opal_path_nfs(), Ralph found this link that shows that fuse has had a history of problems with statfs(). They suggest parsing /proc/mounts or /proc/self/mountinfo instead:
http://comments.gmane.org/gmane.comp.file-systems.fuse.devel/7672
On July 7, 2014, the nightly builds failed due to a failure in the test/util/opal_path_nfs test. I noticed on the build machine, the following mount was present:
It looks like statfs() is lying about the type of filesystem for this mount. Specifically:
According to statfs(2) on RHEL 6.5, 0x6969 is the super magic value for NFS. fuse/encfs is not listed.
I.e., I ''suspect'' that statfs() is confused about the filesystem type of this mount and just gives it an NFS value, especially since there's another mount on this machine:
So I don't know if there's really anything we can do about this -- if statfs() lies to us, I'm not sure what we can do... But I figured I'd file this bug just to record what happened.