Splitmount splits the replicas, leaving the distribution intact and mounts it
through the fuse client. This means that actions performed through the split
mounts go through all the translators except replicate so you don't have to
worry about extended attributes or hardlinks under .glusterfs.
Hi,
We are using fio(https://github.com/axboe/fio) for load/stress testing.
We have not done performance check on a single node.
I will try to verify it.
Thanks,
Kiran.
On Thu, Feb 5, 2015 at 4:47 PM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
+Kiran Patil may know about this.
Hi folks,
Listed below is the initial patchset for the upcoming bitrot detection
feature targeted for GlusterFS 3.7. As of now, these set of patches
implement object signing. Myself and Raghavendra (rabhat@) are working
on pending items (scrubber, etc..) and would be sending those patches
Hi,
These are the patches.
http://review.gluster.org/#/c/9705/
http://review.gluster.org/#/c/9706/
http://review.gluster.org/#/c/9707/
http://review.gluster.org/#/c/9708/
http://review.gluster.org/#/c/9709/
http://review.gluster.org/#/c/9710/
http://review.gluster.org/#/c/9711/
On freshly installed el7 hosts, selinux prevents gluster from running.
Setting selinux to permissive or building the relative .pp module
resolves the issue.
Does otopi configure selinux for gluster when installing?
___
Gluster-users mailing list
Hi all,
Sorry, this question was initially for the ovirt list, but I've been
said that it was a packaging issue, so I come back to you.
The repository where comes from gluster is ovirt-3.5-glusterfs-epel.
Thank you from your help.
Le 19/02/2015 15:43, Nathanaël Blanchet a écrit :
On freshly
I've had issues with the glusterd and glusterfsd sockets getting labeled
var_run_t instead of glusterd_var_run_t.
To fix your problem:
1. Update your hosts to the latest SELinux policy
2. Set SELinux to enforcing
3. Stop any running glusterd or glusterfsd processes. (i.e. systemctl
