search for: spisla80

Hello Gluster Community, I am using Gluster3.10 in a 2-Node-Szenario (with CentosOS7-machines). After restarting one of the nodes, sometimes one of these two phenomena occurs: 1. The brick process of a volume on the newly started node is no longer running 2. The Brick Process Is Running But The First Knot Still Believes He Can not Reach The Brick (Health info reported "Transport

Hello Gluster Community, while reading that article: https://github.com/gluster/glusterfs-specs/blob/master/under_review/worm-compliance.md there seems to be an interesting feature planned for the WORM Xlator: *Scheduled Auto-commit*: Scan Triggered Using timeouts for untouched files. The next scheduled namespace scan will cause the transition. CTR DB via libgfdb can be used to find files that

Hello Gluster Community, according to that set steps I have configured network encryption for management and I/O traffic: https://www.cyberciti.biz/faq/how-to-enable-tlsssl-encryption-with-glusterfs-storage-cluster-on-linux/ I have chose the option for self-signed certificates, so each of the nodes has its own certificate and all of them are stored in the file glusterfs.ca. Each node in my

Hi there, I think this bug, I have found recently, seems to be not trivial: https://bugzilla.redhat.com/show_bug.cgi?id=1558507 In my opinion, it is a violation against the WORM defintion. Discussions are welcome ;-) Regards David Spisla -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello Gluster Community, I did some experiments with setting the atime in different scenarios. In scenario 2,3 and 4 I have a simple replica 2 volume with worm-file-level on 1. Setting atime on XFS: *[davids at gluster-test1 src]$ touch test[davids at gluster-test1 src]$ sudo touch -a -t 197001010001 test[davids at gluster-test1 src]$ stat test File: ?test? Size: 0