[Gluster-users] Strange file corruption

[Udo Giacomozzi]

Am 07.12.2015 um 15:01 schrieb Lindsay Mathieson:
>
>
> On 7/12/2015 9:03 PM, Udo Giacomozzi wrote:
>> Setup details:
>> - Proxmox 4.0 cluster (not yet in HA mode) = Debian 8 Jessie
>> - redundant Gbit LAN (bonding)
>> - Gluster 3.5.2 (most current Proxmox package)
>> - two volumes, both "replicate" type, 1 x 3 = 3 bricks
>> - cluster.server-quorum-ratio: 51%
>
>
> Probably post the output from "gluster volume info" as well.

Hi Lindsay,

as requested:

# gluster volume info

Volume Name: docker-repo
Type: Replicate
Volume ID: d762efae-d558-466b-bb4b-8c698ff90569
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: metal1:/data/gluster/docker-repo
Brick2: metal2:/data/gluster/docker-repo
Brick3: metal3:/data/gluster/docker-repo
Options Reconfigured:
cluster.server-quorum-ratio: 51%

Volume Name: systems
Type: Replicate
Volume ID: b2d72784-4b0e-4f7b-b858-4ec59979a064
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: metal1:/data/gluster/systems
Brick2: metal2:/data/gluster/systems
Brick3: metal3:/data/gluster/systems
Options Reconfigured:
cluster.server-quorum-ratio: 51%


...and also:

# gluster volume heal "systems" info
Brick metal1:/data/gluster/systems/
Number of entries: 0

Brick metal2:/data/gluster/systems/
Number of entries: 0

Brick metal3:/data/gluster/systems/
Number of entries: 0


Simular output for volume "docker-repo".

Udo