Re: [Gluster-devel] Spurious regression failure? tests/basic/ec/ec-background-heals.t

2017-01-26 Thread Pranith Kumar Karampuri 
On Thu, Jan 26, 2017 at 7:45 PM, Ashish Pandey  wrote:

>
> Xavi,
>
> shd has been disabled in this test on line number 12 and we have also
> disabled client side heal.
> So, no body is going to try to heal it.
>

Already enqueued heals should be healed. I am taking a look at it. Let's
see.


>
> Ashish
>
> --
> *From: *"Atin Mukherjee" 
> *To: *"Ashish Pandey" , "Raghavendra Gowdappa" <
> rgowd...@redhat.com>, "Xavier Hernandez" 
> *Cc: *"Gluster Devel" 
> *Sent: *Thursday, January 26, 2017 5:50:00 PM
> *Subject: *Re: [Gluster-devel] Spurious regression failure?
> tests/basic/ec/ec-background-heals.t
>
>
> I've +1ed it now.
>
> On Thu, 26 Jan 2017 at 15:05, Xavier Hernandez 
> wrote:
>
>> Hi Atin,
>>
>> I don't clearly see what's the problem. Even if the truncate causes a
>> dirty flag to be set, eventually it should be removed before the
>> $HEAL_TIMEOUT value.
>>
>> For now I've marked the test as bad.
>>
>> Patch is: https://review.gluster.org/16470
>>
>> Xavi
>>
>> On 25/01/17 17:24, Atin Mukherjee wrote:
>> > Can we please address this as early as possible, my patch has hit this
>> > failure 3 out of 4 recheck attempts now. I'm guessing some recent
>> > changes has caused it.
>> >
>> > On Wed, 25 Jan 2017 at 12:10, Ashish Pandey > > > wrote:
>> >
>> >
>> > Pranith,
>> >
>> > In this test tests/basic/ec/ec-background-heals.t, I think the line
>> > number 86 actually creating a heal entry instead of
>> > helping data heal quickly. What if all the data was already healed
>> > at that moment, truncate came and in preop set the dirty flag and
>> at the
>> > end, as part of the heal, dirty flag was unset on previous good
>> > bricks only and the brick which acted as heal-sink still has dirty
>> > marked by truncate.
>> > That is why we are only seeing "1" as get_pending_heal_count. If a
>> > file was actually not healed it should be "2".
>> > If heal on this file completes and unset of dirty flag happens
>> > before truncate everything will be fine.
>> >
>> > I think we can wait for file to be heal without truncate?
>> >
>> >  71 #Test that disabling background-heals still drains the queue
>> >  72 TEST $CLI volume set $V0 disperse.background-heals 1
>> >  73 TEST touch $M0/{a,b,c,d}
>> >  74 TEST kill_brick $V0 $H0 $B0/${V0}2
>> >  75 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "1" mount_get_option_value
>> > $M0 $V0-disperse-0 background-heals
>> >  76 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "200"
>> > mount_get_option_value $M0 $V0-disperse-0 heal-wait-qlength
>> >  77 TEST truncate -s 1GB $M0/a
>> >  78 echo abc > $M0/b
>> >  79 echo abc > $M0/c
>> >  80 echo abc > $M0/d
>> >  81 TEST $CLI volume start $V0 force
>> >  82 EXPECT_WITHIN $CHILD_UP_TIMEOUT "3" ec_child_up_count $V0 0
>> >  83 TEST chown root:root $M0/{a,b,c,d}
>> >  84 TEST $CLI volume set $V0 disperse.background-heals 0
>> >  85 EXPECT_NOT "0" mount_get_option_value $M0 $V0-disperse-0
>> > heal-waiters
>> >
>> >  86 TEST truncate -s 0 $M0/a # This completes the heal fast ;-)
>> <<<
>> >
>> >  87 EXPECT_WITHIN $HEAL_TIMEOUT "^0$" get_pending_heal_count $V0
>> >
>> > 
>> > Ashish
>> >
>> >
>> >
>> >
>> >
>> > ---
>> -
>> > *From: *"Raghavendra Gowdappa" > > >
>> > *To: *"Nithya Balachandran" > > >
>> > *Cc: *"Gluster Devel" > > >, "Pranith Kumar Karampuri"
>> > mailto:pkara...@redhat.com>>, "Ashish Pandey"
>> > mailto:aspan...@redhat.com>>
>> > *Sent: *Wednesday, January 25, 2017 9:41:38 AM
>> > *Subject: *Re: [Gluster-devel] Spurious regression
>> > failure?tests/basic/ec/ec-background-heals.t
>> >
>> >
>> > Found another failure on same test:
>> > https://build.gluster.org/job/centos6-regression/2874/consoleFull
>> >
>> > - Original Message -
>> > > From: "Nithya Balachandran" > > >
>> > > To: "Gluster Devel" > > >, "Pranith Kumar Karampuri"
>> > mailto:pkara...@redhat.com>>, "Ashish Pandey"
>> > > mailto:aspan...@redhat.com>>
>> > > Sent: Tuesday, January 24, 2017 9:16:31 AM
>> > > Subject: [Gluster-devel] Spurious regression
>> > failure?tests/basic/ec/ec-background-heals.t
>> > >
>> > > Hi,
>> > >
>> > >
>> > > Can you please take a look at
>> > > https://build.gluster.org/job/centos6-regression/2859/console ?
>> > >
>> > > tests/basic/ec/ec-background-heals.t has failed.
>> > >
>> > > Thanks,
>> > > Nithya
>> > >
>> > > ___
>> > > Gluster-devel mailing list
>> > > Gluster-devel@gluster.org

Re: [Gluster-devel] Release 3.10: Branched!

2017-01-26 Thread Shyam 

On 01/19/2017 06:21 AM, Shyam wrote:

Hi,

Release 3.10 has been branched, the following commands give the required
information about the branch and the tags.

2) We have taken some features into consideration for a backport to 3.10
(as follows), so till then we will retain the branch at alpha, and maybe
not even generate required tarballs or RPMs from the same till we reach
a beta state (a week from now, 26th Jan. 2017).

Feature exceptions:
  - https://github.com/gluster/glusterfs/issues/65 (Disabling auto trash
directory creation)
  - https://github.com/gluster/glusterfs/issues/63 (statedump support
for gfapi)
  - https://github.com/gluster/glusterfs/issues/66 (Brick multiplexing)
  - https://github.com/gluster/glusterfs/issues/58 (rebalance time to
completion estimation)
  - https://github.com/gluster/glusterfs/issues/59 (switch to storhaug
for Ganesha and SAMBA HA)


We have most of the pending feature as above into the branch. We are 
still going to wait for the brick multiplexing patch. So tentatively 
tagging this branch for beta1 of 3.10 has been pushed to 30th Jan, 2017.


We will keep the lists updated on the daily progress from there on.

An early heads up, for each component we will raise github issues for 
testing and assign the same to the maintainer of the component. The 
intention being, either provide the testing inputs or reassign it to 
whoever is testing the release with that component in focus and once 
testing is done, update the tests details and close the issue.


The above also serves as a quick tracker to see from which components we 
are expecting testing inputs pre release.




Keep those reviews coming and let's get to the beta stage a week from now!

Thanks,
Kaleb, Talur, Shyam

[1] rfc.sh update: git log 3bed8373a9e3dd290c614185ae8d2fd9e7f0ec86 -1
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Release 3.10: Backport queue status

2017-01-26 Thread Shyam 
As the release-3.10 branch is locked for merge rights across the 3 
release owners (Kaleb, Talur and myself). Here is a handy gerrit 
dashboard for things that are backported to 3.10 and their status.


Link: http://bit.ly/2ky6VPI

The intention of the above dashboard is for us as the release owners to 
act quickly on the first part of the dashboard i.e "Possible To Merge" 
section.


The other intention is for the devel group to accelerate things in the 
remaining 2 sections ("Awaiting Reviews Or Regression" and "Regression 
Failure Or Review Action Needed") in order to get the patches ready for 
merging.


Hope this helps,
Shyam
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Release 3.10: Backports (reminder and action needed)

2017-01-26 Thread Shyam 

Hi,

As we have branched release 3.10 (some time ago), patches that are being 
backported to 3.8/9 and are *applicable* to 3.10 need to be backported 
to 3.10 as well.


An analysis of this state since branching shows the following commits in 
3.9 not backported to 3.10. Ashish, request you to address this at your 
convenience.


bc1ce55a7c83c7f5394b26a65bd4a3a669b5962a (Ashish Pandey) Wed, 11 Jan 
2017 17:19:30 +0530 cluster/ec: Do not start heal on good file while IO 
is going on


0f63bda0df91ee7ff42e3262c74220178ef87a21 (Ashish Pandey) Thu, 19 Jan 
2017 18:20:44 +0530 cluster/disperse: Do not log fop failed for lockless 
fops


Thanks,
Shyam
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Spurious regression failure? tests/basic/ec/ec-background-heals.t

2017-01-26 Thread Ashish Pandey 

Xavi, 

shd has been disabled in this test on line number 12 and we have also disabled 
client side heal. 
So, no body is going to try to heal it. 

Ashish 

- Original Message -

From: "Atin Mukherjee"  
To: "Ashish Pandey" , "Raghavendra Gowdappa" 
, "Xavier Hernandez"  
Cc: "Gluster Devel"  
Sent: Thursday, January 26, 2017 5:50:00 PM 
Subject: Re: [Gluster-devel] Spurious regression failure? 
tests/basic/ec/ec-background-heals.t 

I've +1ed it now. 

On Thu, 26 Jan 2017 at 15:05, Xavier Hernandez < xhernan...@datalab.es > wrote: 


Hi Atin, 

I don't clearly see what's the problem. Even if the truncate causes a 
dirty flag to be set, eventually it should be removed before the 
$HEAL_TIMEOUT value. 

For now I've marked the test as bad. 

Patch is: https://review.gluster.org/16470 

Xavi 

On 25/01/17 17:24, Atin Mukherjee wrote: 
> Can we please address this as early as possible, my patch has hit this 
> failure 3 out of 4 recheck attempts now. I'm guessing some recent 
> changes has caused it. 
> 
> On Wed, 25 Jan 2017 at 12:10, Ashish Pandey < aspan...@redhat.com 
> > wrote: 
> 
> 
> Pranith, 
> 
> In this test tests/basic/ec/ec-background-heals.t, I think the line 
> number 86 actually creating a heal entry instead of 
> helping data heal quickly. What if all the data was already healed 
> at that moment, truncate came and in preop set the dirty flag and at the 
> end, as part of the heal, dirty flag was unset on previous good 
> bricks only and the brick which acted as heal-sink still has dirty 
> marked by truncate. 
> That is why we are only seeing "1" as get_pending_heal_count. If a 
> file was actually not healed it should be "2". 
> If heal on this file completes and unset of dirty flag happens 
> before truncate everything will be fine. 
> 
> I think we can wait for file to be heal without truncate? 
> 
> 71 #Test that disabling background-heals still drains the queue 
> 72 TEST $CLI volume set $V0 disperse.background-heals 1 
> 73 TEST touch $M0/{a,b,c,d} 
> 74 TEST kill_brick $V0 $H0 $B0/${V0}2 
> 75 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "1" mount_get_option_value 
> $M0 $V0-disperse-0 background-heals 
> 76 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "200" 
> mount_get_option_value $M0 $V0-disperse-0 heal-wait-qlength 
> 77 TEST truncate -s 1GB $M0/a 
> 78 echo abc > $M0/b 
> 79 echo abc > $M0/c 
> 80 echo abc > $M0/d 
> 81 TEST $CLI volume start $V0 force 
> 82 EXPECT_WITHIN $CHILD_UP_TIMEOUT "3" ec_child_up_count $V0 0 
> 83 TEST chown root:root $M0/{a,b,c,d} 
> 84 TEST $CLI volume set $V0 disperse.background-heals 0 
> 85 EXPECT_NOT "0" mount_get_option_value $M0 $V0-disperse-0 
> heal-waiters 
> 
> 86 TEST truncate -s 0 $M0/a # This completes the heal fast ;-) <<< 
> 
> 87 EXPECT_WITHIN $HEAL_TIMEOUT "^0$" get_pending_heal_count $V0 
> 
>  
> Ashish 
> 
> 
> 
> 
> 
>  
> *From: *"Raghavendra Gowdappa" < rgowd...@redhat.com 
> > 
> *To: *"Nithya Balachandran" < nbala...@redhat.com 
> > 
> *Cc: *"Gluster Devel" < gluster-devel@gluster.org 
> >, "Pranith Kumar Karampuri" 
> < pkara...@redhat.com >, "Ashish Pandey" 
> < aspan...@redhat.com > 
> *Sent: *Wednesday, January 25, 2017 9:41:38 AM 
> *Subject: *Re: [Gluster-devel] Spurious regression 
> failure? tests/basic/ec/ec-background-heals.t 
> 
> 
> Found another failure on same test: 
> https://build.gluster.org/job/centos6-regression/2874/consoleFull 
> 
> - Original Message - 
> > From: "Nithya Balachandran" < nbala...@redhat.com 
> > 
> > To: "Gluster Devel" < gluster-devel@gluster.org 
> >, "Pranith Kumar Karampuri" 
> < pkara...@redhat.com >, "Ashish Pandey" 
> > < aspan...@redhat.com > 
> > Sent: Tuesday, January 24, 2017 9:16:31 AM 
> > Subject: [Gluster-devel] Spurious regression 
> failure? tests/basic/ec/ec-background-heals.t 
> > 
> > Hi, 
> > 
> > 
> > Can you please take a look at 
> > https://build.gluster.org/job/centos6-regression/2859/console ? 
> > 
> > tests/basic/ec/ec-background-heals.t has failed. 
> > 
> > Thanks, 
> > Nithya 
> > 
> > ___ 
> > Gluster-devel mailing list 
> > Gluster-devel@gluster.org  
> > http://lists.gluster.org/mailman/listinfo/gluster-devel 
> ___ 
> 
> Gluster-devel mailing list 
> 
> Gluster-devel@gluster.org  
> 
> http://lists.gluster.org/mailman/listinfo/gluster-devel 
> 
> -- 
> - Atin (atinm) 
> 
> 
> ___ 
> Gluster-devel mailing list 
> Gluster-devel@gluster.org 
> http://lists.gluster.org/mailman/listinfo/gluster-devel 
> 




-- 
- Atin (atinm) 

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Spurious regression failure? tests/basic/ec/ec-background-heals.t

2017-01-26 Thread Atin Mukherjee 
I've +1ed it now.

On Thu, 26 Jan 2017 at 15:05, Xavier Hernandez 
wrote:

> Hi Atin,
>
> I don't clearly see what's the problem. Even if the truncate causes a
> dirty flag to be set, eventually it should be removed before the
> $HEAL_TIMEOUT value.
>
> For now I've marked the test as bad.
>
> Patch is: https://review.gluster.org/16470
>
> Xavi
>
> On 25/01/17 17:24, Atin Mukherjee wrote:
> > Can we please address this as early as possible, my patch has hit this
> > failure 3 out of 4 recheck attempts now. I'm guessing some recent
> > changes has caused it.
> >
> > On Wed, 25 Jan 2017 at 12:10, Ashish Pandey  > > wrote:
> >
> >
> > Pranith,
> >
> > In this test tests/basic/ec/ec-background-heals.t, I think the line
> > number 86 actually creating a heal entry instead of
> > helping data heal quickly. What if all the data was already healed
> > at that moment, truncate came and in preop set the dirty flag and at
> the
> > end, as part of the heal, dirty flag was unset on previous good
> > bricks only and the brick which acted as heal-sink still has dirty
> > marked by truncate.
> > That is why we are only seeing "1" as get_pending_heal_count. If a
> > file was actually not healed it should be "2".
> > If heal on this file completes and unset of dirty flag happens
> > before truncate everything will be fine.
> >
> > I think we can wait for file to be heal without truncate?
> >
> >  71 #Test that disabling background-heals still drains the queue
> >  72 TEST $CLI volume set $V0 disperse.background-heals 1
> >  73 TEST touch $M0/{a,b,c,d}
> >  74 TEST kill_brick $V0 $H0 $B0/${V0}2
> >  75 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "1" mount_get_option_value
> > $M0 $V0-disperse-0 background-heals
> >  76 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "200"
> > mount_get_option_value $M0 $V0-disperse-0 heal-wait-qlength
> >  77 TEST truncate -s 1GB $M0/a
> >  78 echo abc > $M0/b
> >  79 echo abc > $M0/c
> >  80 echo abc > $M0/d
> >  81 TEST $CLI volume start $V0 force
> >  82 EXPECT_WITHIN $CHILD_UP_TIMEOUT "3" ec_child_up_count $V0 0
> >  83 TEST chown root:root $M0/{a,b,c,d}
> >  84 TEST $CLI volume set $V0 disperse.background-heals 0
> >  85 EXPECT_NOT "0" mount_get_option_value $M0 $V0-disperse-0
> > heal-waiters
> >
> >  86 TEST truncate -s 0 $M0/a # This completes the heal fast ;-)
> <<<
> >
> >  87 EXPECT_WITHIN $HEAL_TIMEOUT "^0$" get_pending_heal_count $V0
> >
> > 
> > Ashish
> >
> >
> >
> >
> >
> >
>  
> > *From: *"Raghavendra Gowdappa"  > >
> > *To: *"Nithya Balachandran"  > >
> > *Cc: *"Gluster Devel"  > >, "Pranith Kumar Karampuri"
> > mailto:pkara...@redhat.com>>, "Ashish Pandey"
> > mailto:aspan...@redhat.com>>
> > *Sent: *Wednesday, January 25, 2017 9:41:38 AM
> > *Subject: *Re: [Gluster-devel] Spurious regression
> > failure?tests/basic/ec/ec-background-heals.t
> >
> >
> > Found another failure on same test:
> > https://build.gluster.org/job/centos6-regression/2874/consoleFull
> >
> > - Original Message -
> > > From: "Nithya Balachandran"  > >
> > > To: "Gluster Devel"  > >, "Pranith Kumar Karampuri"
> > mailto:pkara...@redhat.com>>, "Ashish Pandey"
> > > mailto:aspan...@redhat.com>>
> > > Sent: Tuesday, January 24, 2017 9:16:31 AM
> > > Subject: [Gluster-devel] Spurious regression
> > failure?tests/basic/ec/ec-background-heals.t
> > >
> > > Hi,
> > >
> > >
> > > Can you please take a look at
> > > https://build.gluster.org/job/centos6-regression/2859/console ?
> > >
> > > tests/basic/ec/ec-background-heals.t has failed.
> > >
> > > Thanks,
> > > Nithya
> > >
> > > ___
> > > Gluster-devel mailing list
> > > Gluster-devel@gluster.org 
> > > http://lists.gluster.org/mailman/listinfo/gluster-devel
> > ___
> >
> > Gluster-devel mailing list
> >
> > Gluster-devel@gluster.org 
> >
> > http://lists.gluster.org/mailman/listinfo/gluster-devel
> >
> > --
> > - Atin (atinm)
> >
> >
> > ___
> > Gluster-devel mailing list
> > Gluster-devel@gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-devel
> >
>
> --
- Atin (atinm)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Spurious regression failure? tests/basic/ec/ec-background-heals.t

2017-01-26 Thread Xavier Hernandez 

Hi Atin,

I don't clearly see what's the problem. Even if the truncate causes a 
dirty flag to be set, eventually it should be removed before the 
$HEAL_TIMEOUT value.


For now I've marked the test as bad.

Patch is: https://review.gluster.org/16470

Xavi

On 25/01/17 17:24, Atin Mukherjee wrote:

Can we please address this as early as possible, my patch has hit this
failure 3 out of 4 recheck attempts now. I'm guessing some recent
changes has caused it.

On Wed, 25 Jan 2017 at 12:10, Ashish Pandey mailto:aspan...@redhat.com>> wrote:


Pranith,

In this test tests/basic/ec/ec-background-heals.t, I think the line
number 86 actually creating a heal entry instead of
helping data heal quickly. What if all the data was already healed
at that moment, truncate came and in preop set the dirty flag and at the
end, as part of the heal, dirty flag was unset on previous good
bricks only and the brick which acted as heal-sink still has dirty
marked by truncate.
That is why we are only seeing "1" as get_pending_heal_count. If a
file was actually not healed it should be "2".
If heal on this file completes and unset of dirty flag happens
before truncate everything will be fine.

I think we can wait for file to be heal without truncate?

 71 #Test that disabling background-heals still drains the queue
 72 TEST $CLI volume set $V0 disperse.background-heals 1
 73 TEST touch $M0/{a,b,c,d}
 74 TEST kill_brick $V0 $H0 $B0/${V0}2
 75 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "1" mount_get_option_value
$M0 $V0-disperse-0 background-heals
 76 EXPECT_WITHIN $CONFIG_UPDATE_TIMEOUT "200"
mount_get_option_value $M0 $V0-disperse-0 heal-wait-qlength
 77 TEST truncate -s 1GB $M0/a
 78 echo abc > $M0/b
 79 echo abc > $M0/c
 80 echo abc > $M0/d
 81 TEST $CLI volume start $V0 force
 82 EXPECT_WITHIN $CHILD_UP_TIMEOUT "3" ec_child_up_count $V0 0
 83 TEST chown root:root $M0/{a,b,c,d}
 84 TEST $CLI volume set $V0 disperse.background-heals 0
 85 EXPECT_NOT "0" mount_get_option_value $M0 $V0-disperse-0
heal-waiters

 86 TEST truncate -s 0 $M0/a # This completes the heal fast ;-) <<<

 87 EXPECT_WITHIN $HEAL_TIMEOUT "^0$" get_pending_heal_count $V0


Ashish






*From: *"Raghavendra Gowdappa" mailto:rgowd...@redhat.com>>
*To: *"Nithya Balachandran" mailto:nbala...@redhat.com>>
*Cc: *"Gluster Devel" mailto:gluster-devel@gluster.org>>, "Pranith Kumar Karampuri"
mailto:pkara...@redhat.com>>, "Ashish Pandey"
mailto:aspan...@redhat.com>>
*Sent: *Wednesday, January 25, 2017 9:41:38 AM
*Subject: *Re: [Gluster-devel] Spurious regression
failure?tests/basic/ec/ec-background-heals.t


Found another failure on same test:
https://build.gluster.org/job/centos6-regression/2874/consoleFull

- Original Message -
> From: "Nithya Balachandran" mailto:nbala...@redhat.com>>
> To: "Gluster Devel" mailto:gluster-devel@gluster.org>>, "Pranith Kumar Karampuri"
mailto:pkara...@redhat.com>>, "Ashish Pandey"
> mailto:aspan...@redhat.com>>
> Sent: Tuesday, January 24, 2017 9:16:31 AM
> Subject: [Gluster-devel] Spurious regression
failure?tests/basic/ec/ec-background-heals.t
>
> Hi,
>
>
> Can you please take a look at
> https://build.gluster.org/job/centos6-regression/2859/console ?
>
> tests/basic/ec/ec-background-heals.t has failed.
>
> Thanks,
> Nithya
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org 
> http://lists.gluster.org/mailman/listinfo/gluster-devel
___

Gluster-devel mailing list

Gluster-devel@gluster.org 

http://lists.gluster.org/mailman/listinfo/gluster-devel

--
- Atin (atinm)


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel



___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel