On 09/05/2014 03:51 PM, Kaushal M wrote:
GlusterD performs the following functions as the management daemon for
GlusterFS:
- Peer membership management
- Maintains consistency of configuration data across nodes
(distributed configuration store)
- Distributed command execution (orchestration)
What is the glusterfs version where you ran into this issue?
Pranith
On 09/05/2014 11:52 PM, Ramesh Natarajan wrote:
I have a replicate glusterfs setup on 3 Bricks ( replicate = 3 ). I
have client and server quorum turned on. I rebooted one of the 3
bricks. When it came back up, the client
3.5.2 installed via rpm from official gluster repo, running on amazon ami.
Thanks
Ramesh
On Sep 6, 2014, at 7:29 AM, Pranith Kumar Karampuri pkara...@redhat.com
wrote:
What is the glusterfs version where you ran into this issue?
Pranith
On 09/05/2014 11:52 PM, Ramesh Natarajan wrote:
On 09/06/2014 06:17 PM, Ramesh Natarajan wrote:
3.5.2 installed via rpm from official gluster repo, running on amazon ami.
Including the client i.e. mount bits?
Pranith
Thanks
Ramesh
On Sep 6, 2014, at 7:29 AM, Pranith Kumar Karampuri
pkara...@redhat.com mailto:pkara...@redhat.com wrote:
Justin Clift jus...@gluster.org wrote:
Does this mean we'll need to learn Go as well as C and Python?
If so, that doesn't sound completely optimal. :/
I agree with that. Fancy new languages are cool and full of nice
features, but they reduce the amount of possible contributors. If you
feel you
Client is also running the same version. It is running RHEL 6.5.
The mount command used is
mount -t glusterfs -o
On 09/06/2014 04:53 AM, Jeff Darcy wrote:
I have a replicate glusterfs setup on 3 Bricks ( replicate = 3 ). I have
client and server quorum turned on. I rebooted one of the 3 bricks. When it
came back up, the client started throwing error messages that one of the
files went into split brain.
On 09/06/2014 05:55 PM, Pranith Kumar Karampuri wrote:
On 09/05/2014 03:51 PM, Kaushal M wrote:
GlusterD performs the following functions as the management daemon for
GlusterFS:
- Peer membership management
- Maintains consistency of configuration data across nodes
(distributed
I upgraded the client to Gluster 3.5.2, but there is no difference.
The bug is almost certainly in the Fuse client. If I remount the filesystem
with NFS, the problem is no longer observable.
I spent a little time looking through the xlator/fuse-bridge to see where the
offsets are coming from,
Thanks Mike, this is good stuff. :)
+ Justin
On 06/09/2014, at 8:19 PM, mike wrote:
I upgraded the client to Gluster 3.5.2, but there is no difference.
The bug is almost certainly in the Fuse client. If I remount the filesystem
with NFS, the problem is no longer observable.
I spent a
I was able to narrow it down to smallish python script.
I've attached that to the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1138970
On Sep 6, 2014, at 1:05 PM, Justin Clift jus...@gluster.org wrote:
Thanks Mike, this is good stuff. :)
+ Justin
On 06/09/2014, at 8:19 PM, mike
11 matches
Mail list logo
