search for: d5ee

Yes, the shds did pick up the file for healing (I saw messages like " got entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error afterwards. Anyway I reproduced it by manually setting the afr.dirty bit for a zero byte file on all 3 bricks. Since there are no afr pending xattrs indicating good/bad copies and all files are zero bytes, the data self-heal algorithm just picks the fi...

...ishankar at redhat.com > > To: mabi <mabi at protonmail.ch> > > Ben Turner <bturner at redhat.com>, Gluster Users <gluster-users at gluster.org> > > > > Yes, the shds did pick up the file for healing (I saw messages like " got > > entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error afterwards. > > > > Anyway I reproduced it by manually setting the afr.dirty bit for a zero > > byte file on all 3 bricks. Since there are no afr pending xattrs > > indicating good/bad copies and all files are zero bytes, the data &...

...7, 2017 1:45 PM > From: ravishankar at redhat.com > To: mabi <mabi at protonmail.ch> > Ben Turner <bturner at redhat.com>, Gluster Users <gluster-users at gluster.org> > > Yes, the shds did pick up the file for healing (I saw messages like " got entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error afterwards. > > Anyway I reproduced it by manually setting the afr.dirty bit for a zero byte file on all 3 bricks. Since there are no afr pending xattrs indicating good/bad copies and all files are zero bytes, the data self-heal algorithm just picks...

...> To: mabi <mabi at protonmail.ch> >>>> Ben Turner <bturner at redhat.com>, Gluster Users <gluster-users at gluster.org> >>>> >>>> Yes, the shds did pick up the file for healing (I saw messages like " got >>>> entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error afterwards. >>>> >>>> Anyway I reproduced it by manually setting the afr.dirty bit for a zero >>>> byte file on all 3 bricks. Since there are no afr pending xattrs >>>> indicating good/bad copies and all file...

...hat.com >>> To: mabi <mabi at protonmail.ch> >>> Ben Turner <bturner at redhat.com>, Gluster Users <gluster-users at gluster.org> >>> >>> Yes, the shds did pick up the file for healing (I saw messages like " got >>> entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error afterwards. >>> >>> Anyway I reproduced it by manually setting the afr.dirty bit for a zero >>> byte file on all 3 bricks. Since there are no afr pending xattrs >>> indicating good/bad copies and all files are zero bytes...

...gt; >> >>> Ben Turner <bturner at redhat.com>, Gluster Users >> <gluster-users at gluster.org> >> >>> >> >>> Yes, the shds did pick up the file for healing (I saw messages >> like " got >> >>> entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error >> afterwards. >> >>> >> >>> Anyway I reproduced it by manually setting the afr.dirty bit for >> a zero >> >>> byte file on all 3 bricks. Since there are no afr pending xattrs >> >>>...

...com>](mailto:bturner at redhat.com), Gluster Users [<gluster-users at gluster.org>](mailto:gluster-users at gluster.org) >>>>>> >>>>>> Yes, the shds did pick up the file for healing (I saw messages like " got >>>>>> entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error afterwards. >>>>>> >>>>>> Anyway I reproduced it by manually setting the afr.dirty bit for a zero >>>>>> byte file on all 3 bricks. Since there are no afr pending xattrs >>>>>> indicat...

...he volume concerned is called myvol-pro, the other 3 volumes have no problem so far. > > Also note that in the mean time it looks like the file has been deleted by the user and as such the heal info command does not show the file name anymore but just is GFID which is: > > gfid:1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea > > Hope that helps for debugging this issue. > >> -------- Original Message -------- >> Subject: Re: [Gluster-users] self-heal not working >> Local Time: August 24, 2017 5:58 AM >> UTC Time: August 24, 2017 3:58 AM >> From: ravishankar...

...;bturner at redhat.com>, Gluster Users >>>> <gluster-users at gluster.org> >>>> >>> >>>> >>> Yes, the shds did pick up the file for healing (I saw messages >>>> like " got >>>> >>> entry: 1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea") but no error >>>> afterwards. >>>> >>> >>>> >>> Anyway I reproduced it by manually setting the afr.dirty bit >>>> for a zero >>>> >>> byte file on all 3 bricks. Since there are no...

...s in this mail. The volume concerned is called myvol-pro, the other 3 volumes have no problem so far. Also note that in the mean time it looks like the file has been deleted by the user and as such the heal info command does not show the file name anymore but just is GFID which is: gfid:1985e233-d5ee-4e3e-a51a-cf0b5f9f2aea Hope that helps for debugging this issue. > -------- Original Message -------- > Subject: Re: [Gluster-users] self-heal not working > Local Time: August 24, 2017 5:58 AM > UTC Time: August 24, 2017 3:58 AM > From: ravishankar at redhat.com > To: mabi <m...

Unlikely. In your case only the afr.dirty is set, not the afr.volname-client-xx xattr. `gluster volume set myvolume diagnostics.client-log-level DEBUG` is right. On 08/23/2017 10:31 PM, mabi wrote: > I just saw the following bug which was fixed in 3.8.15: > > https://bugzilla.redhat.com/show_bug.cgi?id=1471613 > > Is it possible that the problem I described in this post is

I just saw the following bug which was fixed in 3.8.15: https://bugzilla.redhat.com/show_bug.cgi?id=1471613 Is it possible that the problem I described in this post is related to that bug? > -------- Original Message -------- > Subject: Re: [Gluster-users] self-heal not working > Local Time: August 22, 2017 11:51 AM > UTC Time: August 22, 2017 9:51 AM > From: ravishankar at