Hi all,
Later today we will have an other Gluster Community Bug Triage meeting.
Meeting details:
- location: #gluster-meeting on Freenode IRC
- date: every Tuesday
- time: 12:00 UTC, 13:00 CET (in your terminal, run: date -d 12:00 UTC)
- agenda: https://public.pad.fsfe.org/p/gluster-bug-triage
Hi John,
There seems to a bug in cli command line parsing which is not allowing
options prefixed with double hyphen apart from few. As a workaround to fix
this for now, do following steps.
1. Stop geo-replication session.
2. Add the following at the end of the file
On 11/24/14, 11:56 PM, Atin Mukherjee wrote:
Can you please find/point out the first instance of the command and its
associated glusterd log which failed to acquire the cluster wide lock.
Can you help me identify what I should be looking for in the logs?
I restarted the glusterd service and
On 11/25/2014 01:41 PM, Niels de Vos wrote:
Hi all,
Later today we will have an other Gluster Community Bug Triage meeting.
Meeting details:
- location: #gluster-meeting on Freenode IRC
- date: every Tuesday
- time: 12:00 UTC, 13:00 CET (in your terminal, run: date -d 12:00 UTC)
- agenda:
Hello Gluster experts,
I have been using gluster for a small cluster for a few years now and I
have a question regarding the new disperse feature, which is for me a much
anticipated addition.
*Suppose* I create a volume with a disperse set of 3, redundancy 1 (let's
call them A1, A2, A3) and then
Xavi will be the better person to clear all your doubts on this feature,
however as per my understanding please see the response inline.
~Atin
On 11/25/2014 07:11 PM, Ayelet Shemesh wrote:
Hello Gluster experts,
I have been using gluster for a small cluster for a few years now and I
have a
Is there a way to have the gluster log files date/time stamps use local
timezone. This system is in EST and the times recorded in the logs are
off by 5 hours. I'm assuming logs are represented as UTC/GMT. This is
using Gluster 3.5.2.
Thanks
___
We have three Gluster clusters, all three of which are exhibiting the
same symptom: FUSE clients report network ping timeouts from bricks,
disconnect from the volume, and then very quickly re-connect to all bricks.
An example from the client logs:
[2014-11-20 01:19:09.079725] C
On 11/25/14, 10:06 AM, Atin Mukherjee wrote:
On 11/25/2014 07:08 PM, Scott Merrill wrote:
On 11/24/14, 11:56 PM, Atin Mukherjee wrote:
Can you please find/point out the first instance of the command and its
associated glusterd log which failed to acquire the cluster wide lock.
Can you
I would like to add that all other log files /var/log/messages,
/var/log/syslog, /var/log/secure, etc... have the correct entries using the
local timezone. It is only the gluster log files that are off by 5 hours.
Could someone point me in the right direction on configuring this?This
Gluster
A much simpler answer is to assign a hostname to multiple IP addresses
(round robin dns). When gethostbyname() returns multiple entries, the
client will try them all until it's successful.
On 11/24/2014 06:23 PM, Paul Robert Marino wrote:
This is simple and can be handled in many ways.
Some
I have a fresh install of gluster v3.6.1 on debian:
# dpkg -l|grep gluster
ii glusterfs-client 3.6.1-1
ii glusterfs-common 3.6.1-1
ii glusterfs-server 3.6.1-1
When I issue this command:
# gluster snapshot create 20141125
I have a 2 server CentOS 6 replicated cluster which started out as version
3.3 and has been progressively updated and is now on version 3.6.1.
Yesterday I added a new freshly installed CentOS 6.6 host and wanted to
convert to replica 3 on one of my volumes, however I was unable to add the
brick
Hi Kotresh,
Thank you. Unfortunately, it doesn't seem to have made much difference,
with rsync still hammering the CPU.
regards,
John
On 25/11/14 20:05, Kotresh Hiremath Ravishankar wrote:
Hi John,
There seems to a bug in cli command line parsing which is not allowing
options prefixed
Ah now I see your problem.Have you considered setting it not to mount automatically on boot then add a simple init script which runs after the gluster services have started to mount it.That would effectively solve your problem. However generally you don't want to reboot a the second node in a 2
Hi,
My Glusterfs version is :- glusterfs-3.6.1-1.el7
On Wed, Nov 26, 2014 at 1:59 AM, Kanagaraj Mayilsamy kmayi...@redhat.com
wrote:
[+Gluster-users@gluster.org]
Initialization of volume 'management' failed, review your volfile again,
glusterd throws this error when the service is started
On 11/25/2014 05:59 AM, Derick Turner wrote:
Gluster version is standard Ubuntu 14.04 LTS repo version -
glusterfs 3.4.2 built on Jan 14 2014 18:05:37
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. http://www.gluster.com
GlusterFS comes with
+Kaleb who implemented this feature to see if there is a way to change it.
Pranith
On 11/25/2014 09:04 PM, Koby, Bradley wrote:
I would like to add that all other log files /var/log/messages,
/var/log/syslog, /var/log/secure, etc... have the correct entries
using the local timezone. It is
+Kiran to check if he knows anything about this.
Pranith
On 11/26/2014 02:17 AM, Kiebzak, Jason M. wrote:
I'm running ZFS . It appears that Gluster Snapshots require LVM. I've
spent the last hour googling this, and it doesn't seem like the two
can be mixed -- that is Gluster Snapshots and
Could be this bug, https://bugzilla.redhat.com/show_bug.cgi?id=1168080
Regards,
Poornima
- Original Message -
From: Eric Ewanco eric.ewa...@genband.com
To: gluster-users@gluster.org
Sent: Wednesday, November 26, 2014 12:43:56 AM
Subject: Re: [Gluster-users] Gluster volume not
- Original Message -
From: Jason M. Kiebzak jk3...@cumc.columbia.edu
To: gluster-users@gluster.org gluster-users@gluster.org
Sent: Wednesday, November 26, 2014 2:17:28 AM
Subject: [Gluster-users] ZFS and Snapshots
I’m running ZFS . It appears that Gluster Snapshots require
issue this command:
# gluster snapshot create 20141125 testing
I get this error:
snapshot create: failed: Cluster operating version is lesser than the
supported version for a snapshot
Snapshot command failed
In fact, all gluster snapshot commands fail with the same error
Just wanted to clarify one thing here. If you have a 2 node cluster and
one of the node is down and other is rebooted, the daemons wouldn't get
started until and unless there is no peer in the cluster or atleast a
friend update (happens during handshake) is received. This is to ensure
the node
23 matches
Mail list logo
