On 06/29/2015 08:18 PM, Niels de Vos wrote:
On Wed, Jun 24, 2015 at 07:44:13PM +0530, Soumya Koduri wrote:
On 06/24/2015 10:14 AM, Krishnan Parthasarathi wrote:
- Original Message -
I've been looking at the recent patches to redirect GF_FOP_IPC to an active
subvolume instead of a
On Wed, Jun 24, 2015 at 07:44:13PM +0530, Soumya Koduri wrote:
>
>
> On 06/24/2015 10:14 AM, Krishnan Parthasarathi wrote:
> >
> >
> >- Original Message -
> >>I've been looking at the recent patches to redirect GF_FOP_IPC to an active
> >>subvolume instead of always to the first. Specifi
On 06/25/2015 12:10 PM, Soumya Koduri wrote:
On 06/25/2015 09:00 AM, Pranith Kumar Karampuri wrote:
On 06/25/2015 02:49 AM, Jeff Darcy wrote:
It knows which bricks are up/down. But they may not be the latest.
Will
that matter?
AFAIK it's sufficient at this point to know which are up/dow
On 06/25/2015 09:00 AM, Pranith Kumar Karampuri wrote:
On 06/25/2015 02:49 AM, Jeff Darcy wrote:
It knows which bricks are up/down. But they may not be the latest. Will
that matter?
AFAIK it's sufficient at this point to know which are up/down.
In that case, we need two functions which giv
On 06/25/2015 02:49 AM, Jeff Darcy wrote:
It knows which bricks are up/down. But they may not be the latest. Will
that matter?
AFAIK it's sufficient at this point to know which are up/down.
In that case, we need two functions which give first active child and
next_active_child in case of fail
> It knows which bricks are up/down. But they may not be the latest. Will
> that matter?
AFAIK it's sufficient at this point to know which are up/down.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/glust
On 06/24/2015 08:26 PM, Jeff Darcy wrote:
I haven't seen the patches yet. Failures can happen just at the time of
winding, leading to same failures. It at least needs to have the logic
of picking next_active_child. EC needs to lock+xattrop the bricks to
find bricks with good copies. AFR needs t
> I haven't seen the patches yet. Failures can happen just at the time of
> winding, leading to same failures. It at least needs to have the logic
> of picking next_active_child. EC needs to lock+xattrop the bricks to
> find bricks with good copies. AFR needs to perform getxattr to find good
> copi
On 06/24/2015 07:44 PM, Soumya Koduri wrote:
On 06/24/2015 10:14 AM, Krishnan Parthasarathi wrote:
- Original Message -
I've been looking at the recent patches to redirect GF_FOP_IPC to an
active
subvolume instead of always to the first. Specifically, these:
http://review.g
On 06/24/2015 10:14 AM, Krishnan Parthasarathi wrote:
- Original Message -
I've been looking at the recent patches to redirect GF_FOP_IPC to an active
subvolume instead of always to the first. Specifically, these:
http://review.gluster.org/11346 for DHT
http://review.gluste
- Original Message -
> I've been looking at the recent patches to redirect GF_FOP_IPC to an active
> subvolume instead of always to the first. Specifically, these:
>
>http://review.gluster.org/11346 for DHT
>http://review.gluster.org/11347 for EC
>http://review.gluster.org/1
I've been looking at the recent patches to redirect GF_FOP_IPC to an active
subvolume instead of always to the first. Specifically, these:
http://review.gluster.org/11346 for DHT
http://review.gluster.org/11347 for EC
http://review.gluster.org/11348 for AFR
I can't help but wonder if t
12 matches
Mail list logo
