[Gluster-devel] The return of the all-null pending matrix

[Emmanuel Dreyfus]

Vijay Bellur <vbellur at redhat.com> wrote:

> I have not been able to re-create the problem in my setup. I think it
> would be a good idea to track this bug and address it. For now, can we
> not use the volume set mechanism to disable eager-locking?

One possible odd point: two of my bricks are on the same machine, and I
mix 32 bits systems (silo, hangar) and a 64 bit system (hotstuff)

Type: Distributed-Replicate
Volume ID: 89827705-e57b-4c11-8b44-161f24f55c0a
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: silo:/export/wd3a
Brick2: hangar:/export/wd1a
Brick3: hangar:/export/wd3a
Brick4: hotstuff:/export/wd1a
Options Reconfigured:
cluster.eager-lock: off



-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org