On 05/02/2017 01:08 AM, mabi wrote:
Hi,
I have a two nodes GlusterFS 3.8.11 replicated volume and
just noticed today in the glustershd.log log file a lot of the
following warning messages:
[2017-05-01 18:42:18.004747] W [MSGID: 108034]
[afr-self-heald.c:479:afr_shd_index_sweep]
0-myvolume-replicate-0: unable to get index-dir on
myvolume-client-0
[2017-05-01 18:52:19.004989] W [MSGID: 108034]
[afr-self-heald.c:479:afr_shd_index_sweep]
0-myvolume-replicate-0: unable to get index-dir on
myvolume-client-0
[2017-05-01 19:02:20.004827] W [MSGID: 108034]
[afr-self-heald.c:479:afr_shd_index_sweep]
0-myvolume-replicate-0: unable to get index-dir on
myvolume-client-0
Does someone understand what it means and if I should be
concerned or not? Could it be related that I use ZFS and not XFS
as filesystem?
In replicate volumes, the
/<path-to-backend-brick>/.glusterfs/indices directory of
bricks must contain these sub folders: 'dirty', 'entry-changes' and
'xattrop'. From the messages, it looks like these are missing from
your first brick (myvolume-client-0). Can you check if that is the
case?
-Ravi
Best regards,
M.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
|
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users