I am attempting to setup encrypted user home directories via eCryptfs using gluster as a backend.
Very
simple setup currently has a small two node gluster cluster mounted by a
separate client. Normal gluster client and NFS mount / file options
are working fine. Only log messages I get are:
"Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO"
I am posting in this forum to see if anyone knows of any reason why this may be failing from the Glusterfs side."Either the lower file is not in a valid eCryptfs format, or the key could not be retrieved. Plaintext passthrough mode is not enabled; returning -EIO"
Bug 762976 - (GLUSTER-1244) ecryptfs does not work when the directory to be encrypted is on gluster mount
https://bugzilla.redhat.com/show_bug.cgi?id=762976
A non-empty file created on glusterfs with ecryptfs reports as a file of size zero
https://bugzilla.redhat.com/show_bug.cgi?id=989702#c1
These look to be issues with O_DIRECT usage in fuse.
I was hoping someone might have an idea or remember some of
this to help me figure out if using glusterfs for a backend with
eCryptfs is even an option.
Is it possible that this bug is still the core problem?
"ecryptfs does not work properly over nfs, cifs, samba, WebDAV, or aufs"
https://bugs.launchpad.net/ecryptfs/+bug/277578
"ecryptfs does not work properly over nfs, cifs, samba, WebDAV, or aufs"
https://bugs.launchpad.net/ecryptfs/+bug/277578
It is old but still seems to be open..
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users