[Gluster-devel] eager locks

[Emmanuel Dreyfus]

I am testing eager locks on glusterfs-3.5.0qa3 / NetBSD 6.1.2, and they
seem to work (we disabled them by default for NetBSD on 3.4 release
because they were broken).

How can I be sure the client is using them? On a brick I can do that:
# gluster volume info gfs351
 
Volume Name: gfs351
Type: Distributed-Replicate
Volume ID: d8420bcf-2434-4f77-a39d-37348a9b3645
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: silo:/export/wd2a
Brick2: hangar:/export/wd1a
Brick3: hangar:/export/wd3a
Brick4: debacle:/export/wd1a
Options Reconfigured:
cluster.eager-lock: on

But how can I probe the config client side?

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