On 05/15/2014 08:37 AM, Pranith Kumar Karampuri wrote:
- Original Message -
From: "Kaleb S. KEITHLEY"
To: "Gluster Devel"
Sent: Wednesday, May 14, 2014 5:04:02 PM
Subject: [Gluster-devel] GlusterFS-3.4.4beta is slipping
At last week's community meeting we tentatively agreed that tod
On Fri, May 16, 2014 at 12:06 AM, Krishnan Parthasarathi
wrote:
> Which version of gluster are you using?
3.5.0 on CentOS 6.5 x86_64.
Sorry I forgot to mention it.
Cheers,
James
>
> thanks,
> Krish
>
> - Original Message -
>> Due to some weird automation things, I noticed the following:
Which version of gluster are you using?
thanks,
Krish
- Original Message -
> Due to some weird automation things, I noticed the following:
>
> Given a cluster of hosts A,B,C,D
>
> It turns out that if you restart glusterd on host B while you are
> running volume create on host A, this c
Hi,
When automatically building volumes, a volume create failed:
volume create: puppet: failed: Commit failed on
----. Please check log file for
details.
The funny thing was that 'gluster volume info' showed a normal looking
volume, and starting it worked fine.
A
Due to some weird automation things, I noticed the following:
Given a cluster of hosts A,B,C,D
It turns out that if you restart glusterd on host B while you are
running volume create on host A, this can cause host B to be borked.
This means: glusterd will refuse to start, and the only fix I found
Hey Gluster. I realized that things might have changed at some point,
so I was hoping someone could help me get this straight.
Who can enumerate or provide reference to a list of all the files that
should have specific SELinux attributes in Gluster, and what each of
them is.
Currently, /var/lib/g
On 05/16/2014 07:23 AM, Pranith Kumar Karampuri wrote:
- Original Message -
From: "Ravishankar N"
To: "Pranith Kumar Karampuri" , "Gluster Devel"
Sent: Friday, May 16, 2014 7:15:58 AM
Subject: Re: [Gluster-devel] Need inputs for command deprecation output
On 05/16/2014 06:25 AM, Pra
- Original Message -
> From: "Ravishankar N"
> To: "Pranith Kumar Karampuri" , "Gluster Devel"
>
> Sent: Friday, May 16, 2014 7:15:58 AM
> Subject: Re: [Gluster-devel] Need inputs for command deprecation output
>
> On 05/16/2014 06:25 AM, Pranith Kumar Karampuri wrote:
> > Hi,
> >
On 05/16/2014 06:25 AM, Pranith Kumar Karampuri wrote:
Hi,
As part of changing behaviour of 'volume heal' commands. I want the
commands to show the following output. Any feedback in making them better would
be awesome :-).
root@pranithk-laptop - ~
06:20:10 :) ⚡ gluster volume heal r2 info
- Original Message -
> From: "Anand Avati"
> To: "Pranith Kumar Karampuri"
> Cc: "Gluster Devel"
> Sent: Friday, May 16, 2014 6:30:44 AM
> Subject: Re: [Gluster-devel] Spurious failures because of nfs and snapshots
>
> On Thu, May 15, 2014 at 5:49 PM, Pranith Kumar Karampuri <
> pkara
On Thu, May 15, 2014 at 5:49 PM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
> hi,
> In the latest build I fired for review.gluster.com/7766 (
> http://build.gluster.org/job/regression/4443/console) failed because of
> spurious failure. The script doesn't wait for nfs export to be av
Hi,
As part of changing behaviour of 'volume heal' commands. I want the commands
to show the following output. Any feedback in making them better would be
awesome :-).
root@pranithk-laptop - ~
06:20:10 :) ⚡ gluster volume heal r2 info healed
This command has been deprecated
root@pranithk-la
hi,
In the latest build I fired for review.gluster.com/7766
(http://build.gluster.org/job/regression/4443/console) failed because of
spurious failure. The script doesn't wait for nfs export to be available. I
fixed that, but interestingly I found quite a few scripts with same problem.
Some
On 05/15/2014 09:08 PM, Luis Pabon wrote:
Should we create bugs for each of these, and divide-and-conquer?
That could be of help. First level of consolidation done (with frequency
of test failures) by Justin might be a good list to start with. If we
observe more failures as part of ongoing re
On 05/15/2014 07:57 PM, Niels de Vos wrote:
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs last
night for each of the release-3.4, release-3.5, and master branches.
Should we create bugs for each of these, and divide-and-conquer?
- Luis
On 05/15/2014 10:27 AM, Niels de Vos wrote:
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs
On Thu, May 15, 2014 at 06:05:00PM +0530, Vijay Bellur wrote:
> On 04/30/2014 07:03 PM, Justin Clift wrote:
> >Hi us,
> >
> >Was trying out the GlusterFS regression tests in Rackspace VMs last
> >night for each of the release-3.4, release-3.5, and master branches.
> >
> >The regression test is just
Hi
I have not built master for a while, and now find GNU specific extensions
that are not portable. Since it is not the first time I address them,
I would like to send a reminder about it:
1) bash-specific syntax
Do not write:
test $foo == "bar"
But instead write:
test $foo = "b
The cli changes for disperse volumes are ready for review:
http://review.gluster.org/7782/
Xavi
On Thursday 15 May 2014 10:11:49 Xavier Hernandez wrote:
> Hi Kaushal,
>
> On Tuesday 13 May 2014 20:22:06 Kaushal M wrote:
> > The syntax looks good. If you need help with the cli and glusterd chang
On 04/30/2014 07:03 PM, Justin Clift wrote:
Hi us,
Was trying out the GlusterFS regression tests in Rackspace VMs last
night for each of the release-3.4, release-3.5, and master branches.
The regression test is just a run of "run-tests.sh", from a git
checkout of the appropriate branch.
The go
Hi Kaushal,
On Tuesday 13 May 2014 20:22:06 Kaushal M wrote:
> The syntax looks good. If you need help with the cli and glusterd changes,
> I'll be happy to help.
Thanks. It will be really appreciated.
I think I've a working modification. Not sure if there's something else that
have to be modifi
21 matches
Mail list logo
