Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Pranith Kumar Karampuri
On Thu, Jun 29, 2017 at 8:12 PM, Paolo Margara wrote: > Il 29/06/2017 16:27, Pranith Kumar Karampuri ha scritto: > > > > On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara > wrote: > >> Hi Pranith, >> >> I'm using this guide

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Paolo Margara
Il 29/06/2017 16:27, Pranith Kumar Karampuri ha scritto: > > > On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara > > wrote: > > Hi Pranith, > > I'm using this guide > >

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Pranith Kumar Karampuri
On Thu, Jun 29, 2017 at 7:48 PM, Paolo Margara wrote: > Hi Pranith, > > I'm using this guide https://github.com/nixpanic/glusterdocs/blob/ > f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md > > Definitely my fault, but I think that is better to

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Paolo Margara
Hi Pranith, I'm using this guide https://github.com/nixpanic/glusterdocs/blob/f6d48dc17f2cb6ee4680e372520ec3358641b2bc/Upgrade-Guide/upgrade_to_3.8.md Definitely my fault, but I think that is better to specify somewhere that restarting the service is not enough simply because in many other case,

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Pranith Kumar Karampuri
Paolo, Which document did you follow for the upgrade? We can fix the documentation if there are any issues. On Thu, Jun 29, 2017 at 2:07 PM, Ravishankar N wrote: > On 06/29/2017 01:08 PM, Paolo Margara wrote: > > Hi all, > > for the upgrade I followed this

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Ravishankar N
On 06/29/2017 01:08 PM, Paolo Margara wrote: Hi all, for the upgrade I followed this procedure: * put node in maintenance mode (ensure no client are active) * yum versionlock delete glusterfs* * service glusterd stop * yum update * systemctl daemon-reload * service glusterd start

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-29 Thread Paolo Margara
Hi all, for the upgrade I followed this procedure: * put node in maintenance mode (ensure no client are active) * yum versionlock delete glusterfs* * service glusterd stop * yum update * systemctl daemon-reload * service glusterd start * yum versionlock add glusterfs* * gluster

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-28 Thread Pranith Kumar Karampuri
On Wed, Jun 28, 2017 at 9:45 PM, Ravishankar N wrote: > On 06/28/2017 06:52 PM, Paolo Margara wrote: > >> Hi list, >> >> yesterday I noted the following lines into the glustershd.log log file: >> >> [2017-06-28 11:53:05.000890] W [MSGID: 108034] >>

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-28 Thread Ravishankar N
On 06/28/2017 06:52 PM, Paolo Margara wrote: Hi list, yesterday I noted the following lines into the glustershd.log log file: [2017-06-28 11:53:05.000890] W [MSGID: 108034] [afr-self-heald.c:479:afr_shd_index_sweep] 0-iso-images-repo-replicate-0: unable to get index-dir on

Re: [Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-28 Thread Pranith Kumar Karampuri
hi Paolo, I just checked code in v3.8.12 and it should have been created when the brick starts after you upgrade the node. How did you do the upgrade? On Wed, Jun 28, 2017 at 6:52 PM, Paolo Margara wrote: > Hi list, > > yesterday I noted the following lines into the

[Gluster-users] afr-self-heald.c:479:afr_shd_index_sweep

2017-06-28 Thread Paolo Margara
Hi list, yesterday I noted the following lines into the glustershd.log log file: [2017-06-28 11:53:05.000890] W [MSGID: 108034] [afr-self-heald.c:479:afr_shd_index_sweep] 0-iso-images-repo-replicate-0: unable to get index-dir on iso-images-repo-client-0 [2017-06-28 11:53:05.001146] W [MSGID: