Michael,
Could you try the test with "gluster volume set testgl cluster.eager-lock
off".
If you confirm, we may have to backport the following patch from master/3.5
commit 36b102645ab66d141dcc831e67caa78966d45419
Author: Pranith Kumar K
Date: Tue Jul 30 18:29:15 2013 +0530
cluster/af
- Original Message -
> From: "Torbjørn Thorsen"
> To: gluster-users@gluster.org
> Sent: Wednesday, April 23, 2014 7:52:24 PM
> Subject: [Gluster-users] Self-heal working ? Seeing "background meta-data
> data self-heal failed" in logs
>
> Greetings.
>
> We have a distributed and replic
anything in glusterd log file? glusterd in debug mode (glusterd -LDEBUG)
would provide more logs to debug.
On Tue, Feb 25, 2014 at 8:15 PM, Danny Sauer wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have the current gluster 3.4 running on some RHEL6 systems. For some
> reason
Note also that gluster-devel archives will appear here:
http://supercolony.gluster.org/pipermail/gluster-devel/
And old archives will slowly move over, as we are able to do it. In the
meantime, you can still view older archives here:
http://lists.nongnu.org/archive/html/gluster-devel/
-JM
-
Greetings,
Gluster-devel appears to be down at the moment. I've sent an email to the site
maintainers at nongnu.org, and hopefully there will be a resolution soon.
In the meantime, you may want to send -devel messages through the users list
until everything is back up.
Or we can take the subsc
No, I still haven't heard anything from the community, and I just removed the
ssh keys for the broken systems so they don't try to start up the "bad"
replication configs (which is incredibly ugly). Someday soon I'm planning to
build a test cluster to experiment on, though, and will follow up if
Hi Danny,
Did you get anywhere with this geo-rep issue? I have a similar problem
running on CentOS 6.5 when trying anything other than 'start' with geo-rep.
Thanks,
*Steve *
On Tue, Feb 25, 2014 at 9:45 AM, Danny Sauer wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have the
Hello,
i have a replica gluster with to node ( centos 6.5 )
create gluster with:
gluster volume create testgl replica 2 transport tcp
node1:/gluster/testgl/brick/ node2:/glusterfs/testgl/brick/
info:
gluster volume info
Volume Name: testgl
Type: Replicate
Volume ID: 5c820047-76d2-46c9-908b-5
# gluster volume geo-replication rep1 gluster://10.0.11.4:/rep1 stop
geo-replication command failed
cli.log:
2014-04-24 14:08:03.916112] W [rpc-transport.c:175:rpc_transport_load]
0-rpc-transport: missing 'option transport-type'. defaulting to "socket"
[2014-04-24 14:08:03.918050] I [socket.c:3480
Version: glusterfs-server-3.4.2-1.el6.x86_64
I have an issue where I'm not getting the correct status for
geo-replication, this is shown below. Also I've had issues where I've not
been able to stop geo-replication without using a firewall rule on the
slave. I would get back a cryptic error and not
10 matches
Mail list logo
