Thank you for your assessment, Jayme.
I'll collect the interesting facts and do so.
Chris
On 03.02.20 18:58, Jayme wrote:
Ah, the bug I'm referring to may only apply to replica 3 gluster. You
appear to be using an arbiter. It sounds like you may need to file a bug
for this one
On Mon, Feb
Ah, the bug I'm referring to may only apply to replica 3 gluster. You
appear to be using an arbiter. It sounds like you may need to file a bug
for this one
On Mon, Feb 3, 2020 at 12:05 PM Christoph Köhler <
koeh...@luis.uni-hannover.de> wrote:
> Hello Jayme,
>
> the gluster-config is this:
>
>
Hello Jayme,
the gluster-config is this:
gluster volume info gluvol3
Volume Name: gluvol3
Type: Replicate
Volume ID: 8172ebea-c118-424a-a407-50b2fd87e372
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: glusrv01:/gluster/p1/brick1
Brick2:
Chris, what is the storage configuration? I was under the impression that
there was a bug preventing snapshots from working when using libgfapi on
gluster replica configurations. This is one of the main reasons why I have
been unable to implement libgfapi.
On Mon, Feb 3, 2020 at 10:53 AM
4 matches
Mail list logo
