Here are the steps to reproduce this issue. (gluster version 3.5.2) On one server lab1 (There is another server lab2 for replica 2): [root at lab1 ~]# gluster volume set g1 worm on volume set: success [root at lab1 ~]# gluster volume stop g1 Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y volume stop: g1: success [root at lab1 ~]# gluster volume start g1 volume start: g1: success [root at lab1 ~]# gluster volume info Volume Name: g1 Type: Distributed-Replicate Volume ID: fbd79e82-b079-4d19-ae5a-b4279c31bac3 Status: Started Number of Bricks: 2 x 2 = 4 Transport-type: tcp Bricks: Brick1: lab1:/brick1 Brick2: lab2:/brick1 Brick3: lab1:/brick2 Brick4: lab2:/brick2 Options Reconfigured: diagnostics.brick-log-level: TRACE features.worm: on On client (also be one of the servers lab1): [root at lab1 g1]# mount -t glusterfs -o worm lab1:g1 /mnt process info of the gluster mount process. root 2851 1 0 21:28 ? 00:00:01 /usr/sbin/glusterfs --worm --volfile-server=lab1 --volfile-id=g1 /mnt Here is the log of the client. 2014-09-23 13:28:55.345226] W [client-rpc-fops.c:1632:client3_3_entrylk_cbk] 0-g1-client-0: remote operation failed: Read-only file system [2014-09-23 13:28:55.346172] W [client-rpc-fops.c:1632:client3_3_entrylk_cbk] 0-g1-client-0: remote operation failed: Read-only file system [2014-09-23 13:28:55.346222] I [afr-lk-common.c:1092:afr_lock_blocking] 0-g1-replicate-0: unable to lock on even one child [2014-09-23 13:28:55.346245] I [afr-transaction.c:1295:afr_post_blocking_entrylk_cbk] 0-g1-replicate-0: Blocking entrylks failed. [2014-09-23 13:28:55.346321] W [fuse-bridge.c:1911:fuse_create_cbk] 0-glusterfs-fuse: 5: /test => -1 (Read-only file system) ~ It looks like it fails to lock the directory (?) becuase WORM calls ro_entrylk() which is originally for the read-only feature of the file system. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140923/91b819ad/attachment.html>