search for: mezine

By any chance are you having any redundant peer entries in /var/lib/glusterd/peers directory? Can you please share the content of this folder from all the nodes? On Tue, Jul 4, 2017 at 11:55 PM, Victor Nomura <victor at mezine.com> wrote: > Specifically, I must stop glusterfs-server service on the other nodes in > order to perform any gluster commands on any node. > > > > *From:* Victor Nomura [mailto:victor at mezine.com] > *Sent:* July-04-17 9:41 AM > *To:* 'Atin Mukherjee' > *Cc:...

Specifically, I must stop glusterfs-server service on the other nodes in order to perform any gluster commands on any node. From: Victor Nomura [mailto:victor at mezine.com] Sent: July-04-17 9:41 AM To: 'Atin Mukherjee' Cc: 'gluster-users' Subject: RE: [Gluster-users] Gluster failure due to "0-management: Lock not released for <volumename>" The nodes have all been rebooted numerous times with no difference in outcome. The node...

On Thu, 29 Jun 2017 at 22:51, Victor Nomura <victor at mezine.com> wrote: > Thanks for the reply. What would be the best course of action? The data > on the volume isn?t important right now but I?m worried when our setup goes > to production we don?t have the same situation and really need to recover > our Gluster setup. > > > >...

...uest to first look at the N/W layer and rectify the problems. On Thu, Jun 22, 2017 at 9:30 PM, Atin Mukherjee <amukherj at redhat.com> wrote: Could you attach glusterd.log and cmd_history.log files from all the nodes? On Wed, Jun 21, 2017 at 11:40 PM, Victor Nomura <victor at mezine.com> wrote: Hi All, I?m fairly new to Gluster (3.10.3) and got it going for a couple of months now but suddenly after a power failure in our building it all came crashing down. No client is able to connect after powering back the 3 nodes I have setup. Looking at the logs, it looks like...

...first look at the N/W layer and rectify the problems. On Thu, Jun 22, 2017 at 9:30 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > Could you attach glusterd.log and cmd_history.log files from all the nodes? > > On Wed, Jun 21, 2017 at 11:40 PM, Victor Nomura <victor at mezine.com> wrote: > >> Hi All, >> >> >> >> I?m fairly new to Gluster (3.10.3) and got it going for a couple of >> months now but suddenly after a power failure in our building it all came >> crashing down. No client is able to connect after powering back t...

...From: Atin Mukherjee [mailto:amukherj at redhat.com] Sent: June-30-17 3:40 AM To: Victor Nomura Cc: gluster-users Subject: Re: [Gluster-users] Gluster failure due to "0-management: Lock not released for <volumename>" On Thu, 29 Jun 2017 at 22:51, Victor Nomura <victor at mezine.com> wrote: Thanks for the reply. What would be the best course of action? The data on the volume isn?t important right now but I?m worried when our setup goes to production we don?t have the same situation and really need to recover our Gluster setup. I?m assuming that to redo is to dele...

Could you attach glusterd.log and cmd_history.log files from all the nodes? On Wed, Jun 21, 2017 at 11:40 PM, Victor Nomura <victor at mezine.com> wrote: > Hi All, > > > > I?m fairly new to Gluster (3.10.3) and got it going for a couple of months > now but suddenly after a power failure in our building it all came crashing > down. No client is able to connect after powering back the 3 nodes I have > setup. &g...

Hi All, I'm fairly new to Gluster (3.10.3) and got it going for a couple of months now but suddenly after a power failure in our building it all came crashing down. No client is able to connect after powering back the 3 nodes I have setup. Looking at the logs, it looks like there's some sort of "Lock" placed on the volume which prevents all the clients from connecting to