mabi
2017-May-02 18:18 UTC
[Gluster-users] glustershd: unable to get index-dir on myvolume-client-0
Hi Ravi, Thanks for the pointer, you are totally right the "dirty" directory is missing on my node1. Here is the output of a "ls -la" of both nodes: node1: drw------- 2 root root 2 Apr 28 22:15 entry-changes drw------- 2 root root 2 Mar 6 2016 xattrop node2: drw------- 2 root root 3 May 2 19:57 dirty drw------- 2 root root 2 Apr 28 22:15 entry-changes drw------- 2 root root 3 May 2 19:57 xattrop Now what would be the procedure in order to add the "dirty" directory on node1? Can I simply do an "mkdir dirty" in the indices directory? or do I need to stop the volume before? Regards, M. -------- Original Message -------- Subject: Re: [Gluster-users] glustershd: unable to get index-dir on myvolume-client-0 Local Time: May 2, 2017 10:56 AM UTC Time: May 2, 2017 8:56 AM From: ravishankar at redhat.com To: mabi <mabi at protonmail.ch>, Gluster Users <gluster-users at gluster.org> 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 at gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170502/27845b04/attachment.html>
Ravishankar N
2017-May-03 01:09 UTC
[Gluster-users] glustershd: unable to get index-dir on myvolume-client-0
On 05/02/2017 11:48 PM, mabi wrote:> Hi Ravi, > > Thanks for the pointer, you are totally right the "dirty" directory is > missing on my node1. Here is the output of a "ls -la" of both nodes: > > node1: > drw------- 2 root root 2 Apr 28 22:15 entry-changes > drw------- 2 root root 2 Mar 6 2016 xattrop > > node2: > drw------- 2 root root 3 May 2 19:57 dirty > drw------- 2 root root 2 Apr 28 22:15 entry-changes > drw------- 2 root root 3 May 2 19:57 xattrop > > Now what would be the procedure in order to add the "dirty" directory > on node1? Can I simply do an "mkdir dirty" in the indices directory? > or do I need to stop the volume before? >mkdir should work. The folders are created whenever the brick process is started, so I'm wondering how it went missing in the first place. -Ravi> Regards, > M. > > > >> -------- Original Message -------- >> Subject: Re: [Gluster-users] glustershd: unable to get index-dir on >> myvolume-client-0 >> Local Time: May 2, 2017 10:56 AM >> UTC Time: May 2, 2017 8:56 AM >> From: ravishankar at redhat.com >> To: mabi <mabi at protonmail.ch>, Gluster Users <gluster-users at gluster.org> >> >> >> 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 at gluster.org >>> http://lists.gluster.org/mailman/listinfo/gluster-users >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170503/244e54eb/attachment.html>