Hello everyone,
I have cloned and built today's GlusterFS.
The test tests/basic/uss.t fails.
The console log and /var/log/glusterfs/mnt-glusterfs-0 attached.
Any ideas?
Thanks in advance,
Edward.=
TEST 75 (line 159): fd_close 5
ok 75
RESULT 75: 0
=
Hello Emmanuel,
Could you please replace the file ./tests/encryption/crypt.t
with the attached one, run the last one, and report about results?
Thanks,
Edward.
On Fri, 10 Oct 2014 02:00:28 +0200
m...@netbsd.org (Emmanuel Dreyfus) wrote:
Edward Shishkin edw...@redhat.com wrote:
1) What
On Mon, 6 Oct 2014 12:19:44 +
Emmanuel Dreyfus m...@netbsd.org wrote:
Hi
Hello Emmanuel,
crtypt.t gives me this on a symlink after umount/remount:
[2014-10-06 09:28:17.199230] E [metadata.c:534:open_format_v1]
0-crypt: EMTD verification failed [2014-10-06 09:28:17.200028] W
Hi all,
Unfortunately it is impossible to validate non-trusted volfiles
using existing glusterfs options. Semantic and format of values
passed by the --xlator-option don't allow to deliver trusted
values without compromises with security.
So I have added a new --secure-xlator-option,
Please,
Hello everyone,
In this thread we'll consider in details all issues related to
the management aspects of the feature Transparent encryption in
GlusterFS.
We assume that the reader is familiar with the basic concepts of the
feature Transparent encryption in GlusterFS. See, for example,
slides 1-7
Hello everyone,
Here we provide some basic backgrounds in addition to the manpages at
http://www.gluster.org/community/documentation/index.php?title=Features/disk-encryption
Comments, questions, any your experience are welcome.
Thanks,
Edward.
Transparent encryption and
: Edward Shishkin edw...@redhat.com, Gluster Devel
gluster-devel@gluster.org
Sent: Wednesday, May 21, 2014 10:53:54 AM
Subject: Re: [Gluster-devel] spurios failures in
tests/encryption/crypt.t
There are a few suspicious things going on here..
On Tue, May 20, 2014 at 10:07 PM
On Sat, 17 May 2014 04:28:45 -0400 (EDT)
Pranith Kumar Karampuri pkara...@redhat.com wrote:
hi,
crypt.t is failing regression builds once in a while and most of
the times it is because of the failures just after the remount in the
script.
TEST rm -f $M0/testfile-symlink
TEST rm -f
