On Tuesday 24 June 2014 08:17 PM, Pranith Kumar Karampuri wrote:
Does anyone know why inode_unref is no-op for root inode?
I see the following code in inode.c
static inode_t *
__inode_unref (inode_t *inode)
{
if (!inode)
return NULL;
if
On 06/24/2014 03:45 PM, Gluster Build System wrote:
SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.5.1.tar.gz
This release is made off jenkins-release-73
-- Gluster Build System
___
Gluster-users mailing list
On 06/25/2014 11:52 AM, Raghavendra Bhat wrote:
On Tuesday 24 June 2014 08:17 PM, Pranith Kumar Karampuri wrote:
Does anyone know why inode_unref is no-op for root inode?
I see the following code in inode.c
static inode_t *
__inode_unref (inode_t *inode)
{
if (!inode)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2014-06-24 22:26, Shyamsundar Ranganathan wrote:
- Original Message -
From: Anders Blomdell anders.blomd...@control.lth.se
To: Niels de Vos nde...@redhat.com
Cc: Shyamsundar Ranganathan srang...@redhat.com, Gluster Devel
- Original Message -
For the short-term, wouldn't it be OK to disallow adding bricks that
is not a multiple of group-size?
In the *very* short term, yes. However, I think that will quickly
become an issue for users who try to deploy erasure coding because those
group sizes will
On Wednesday 25 June 2014 08:35:05 Jeff Darcy wrote:
For the short-term, wouldn't it be OK to disallow adding bricks that
is not a multiple of group-size?
In the *very* short term, yes. However, I think that will quickly
become an issue for users who try to deploy erasure coding because
If I understand correctly the proposed data-classification
architecture, each server will have a number of bricks that will be
dynamically modified as needed: as more data-classifying conditions
are defined, a new layer of translators will be added (a new DHT or
AFR, or something else) and
Thanks to everyone who attended and participated in our
Weekly Community Meeting today. :)
The points which stand out as most important/interesting are:
* GlusterFS 3.4.5 beta1 tarball and rpms to be created
soon (next few days likely)
This is pretty much GlusterFS 3.4.4-2 with the
Justin asked me, as the group's official Grumpy Old Man, to send a note
reminding people about the importance of reviewing patches early. Here
it is. As I see it, we've historically had two problems with reviews.
(1) Patches that don't get reviewed at all.
(2) Patches that have to be re-worked
SRC:
http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-release-3.4.tar.gz
This release is made off jenkins-release-78
-- Gluster Build System
___
Gluster-devel mailing list
Gluster-devel@gluster.org
Hi Anders,
There are multiple problems that I see in the test provided, here is answering
one of them and the reason why this occurs. It does get into the code and
functions a bit, but bottom line is that on a code path the setattr that DHT
does, misses setting the SGID bit causing the problem
On 20/06/2014, at 2:32 PM, Matteo Checcucci wrote:
On 06/20/2014 03:05 PM, Ravishankar N wrote:
Yes, just sent a patch for review on master
:http://review.gluster.org/#/c/8135/
Once it gets accepted, will back-port it to the 3.5 branch
I am looking forward to seeing it back-ported and
On 25/06/2014, at 11:19 PM, Justin Clift wrote:
There's a new rackspace-regression-2GB-triggered in Jenkins on
build.gluster.org.
Please ignore it for now. I'm just experimenting with having Gerrit
automatically trigger regression tests.
This seems to be working ok, so I've enabled it.
On 26/06/2014, at 1:40 AM, Pranith Kumar Karampuri wrote:
snip
While I agree with everything you said. Complaining about tabs/spaces should
be done by a script. Something like http://review.gluster.com/#/c/5404
+1
And we can use a git trigger to reject future patches that have tabs in
them.
On 26/06/2014, at 2:12 AM, Pranith Kumar Karampuri wrote:
On 06/26/2014 06:19 AM, Justin Clift wrote:
On 26/06/2014, at 1:40 AM, Pranith Kumar Karampuri wrote:
snip
While I agree with everything you said. Complaining about tabs/spaces
should be done by a script. Something like
15 matches
Mail list logo
