Displaying 2 results from an estimated 2 matches for "16816536533b".
2018 Jan 18
2
Segfaults after upgrade to GlusterFS 3.10.9
...398c4) [0x7f7cb8fa58c4] ) 0-inode: invalid argument: inode [Invalid argument]
This leads to serious availability issues.
Is this a known issue? Any workaround available?
FWIW, my GlusterFS volume looks like this:
Volume Name: gfsvol
Type: Distributed-Replicate
Volume ID: f7985bf3-67e1-49d6-90bf-16816536533b
Status: Started
Snapshot Count: 0
Number of Bricks: 4 x 3 = 12
Transport-type: tcp
Bricks:
Brick1: AAA:/bricks/gfsvol/vol1/volume
Brick2: BBB:/bricks/gfsvol/vol1/volume
Brick3: CCC:/bricks/gfsvol/vol1/volume
Brick4: AAA:/bricks/gfsvol/vol2/volume
Brick5: BBB:/bricks/gfsvol/vol2/volume
Brick6: CCC:/...
2018 Jan 19
0
Segfaults after upgrade to GlusterFS 3.10.9
...ument: inode [Invalid argument]
>
> This leads to serious availability issues.
>
> Is this a known issue? Any workaround available?
>
> FWIW, my GlusterFS volume looks like this:
>
> Volume Name: gfsvol
> Type: Distributed-Replicate
> Volume ID: f7985bf3-67e1-49d6-90bf-16816536533b
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 4 x 3 = 12
> Transport-type: tcp
> Bricks:
> Brick1: AAA:/bricks/gfsvol/vol1/volume
> Brick2: BBB:/bricks/gfsvol/vol1/volume
> Brick3: CCC:/bricks/gfsvol/vol1/volume
> Brick4: AAA:/bricks/gfsvol/vol2/volume
> Br...