[Gluster-users] CentOS 7.2 + Gluster 3.6.3 volume stuck in heal

[Kingsley]

Hi,

Thanks. This is really odd. I've just re-checked the status prior to
restarting the self heal daemon and it has now resolved it all by
itself. It had been stuck like this for ages but decided to fix itself
after me posting to this list! ...

[root at gluster1a-1 ~]# gluster volume heal voicemail info
Brick gluster1a-1.dns99.co.uk:/data/brick/voicemail/
Number of entries: 0

Brick gluster1b-1.dns99.co.uk:/data/brick/voicemail/
Number of entries: 0

Brick gluster2a-1.dns99.co.uk:/data/brick/voicemail/
Number of entries: 0

Brick gluster2b-1.dns99.co.uk:/data/brick/voicemail/
Number of entries: 0

[root at gluster1a-1 ~]#

Cheers,
Kingsley.

On Mon, 2016-05-30 at 03:17 -0400, Anuradha Talur wrote:
> Kingsley,
> 
> Looking at the statedumps provided, I can see blocked locks.
> Could you try restarting self-heal daemon and then getting heal info again?
> 
> To restart self-heal-daemon you will have to run:
> gluster volume start <volname> force
> 
> ----- Original Message -----
> > From: "Kingsley" <gluster at gluster.dogwind.com>
> > To: gluster-users at gluster.org
> > Sent: Friday, May 27, 2016 3:41:15 PM
> > Subject: Re: [Gluster-users] CentOS 7.2 + Gluster 3.6.3 volume stuck in heal
> > 
> > Can nobody help with this?
> > 
> > Cheers,
> > Kingsley.
> > 
> > On Fri, 2016-05-20 at 17:36 +0100, Kingsley wrote:
> > > Hi,
> > > 
> > > We've got a volume that has been stuck in "Possibly undergoing heal"
> > > status for several months. I would like to upgrade gluster to a newer
> > > version but I would feel safer if we could get the volume fixed first.
> > > 
> > > Some info:
> > > 
> > > # gluster volume info voicemail
> > > 
> > > Volume Name: voicemail
> > > Type: Replicate
> > > Volume ID: 8f628d09-60d0-4cb8-8d1a-b7a272c42a23
> > > Status: Started
> > > Number of Bricks: 1 x 4 = 4
> > > Transport-type: tcp
> > > Bricks:
> > > Brick1: gluster1a-1:/data/brick/voicemail
> > > Brick2: gluster1b-1:/data/brick/voicemail
> > > Brick3: gluster2a-1:/data/brick/voicemail
> > > Brick4: gluster2b-1:/data/brick/voicemail
> > > 
> > > 
> > > 
> > > # gluster volume heal voicemail info
> > > Brick gluster1a-1.dns99.co.uk:/data/brick/voicemail/
> > > /borked/Old - Possibly undergoing heal
> > > 
> > > Number of entries: 1
> > > 
> > > Brick gluster1b-1.dns99.co.uk:/data/brick/voicemail/
> > > Number of entries: 0
> > > 
> > > Brick gluster2a-1.dns99.co.uk:/data/brick/voicemail/
> > > /borked/Old - Possibly undergoing heal
> > > 
> > > Number of entries: 1
> > > 
> > > Brick gluster2b-1.dns99.co.uk:/data/brick/voicemail/
> > > /borked/Old - Possibly undergoing heal
> > > 
> > > Number of entries: 1
> > > 
> > > 
> > > There's a statedump here; I've appended the server name to each file (I
> > > grabbed a copy from each server, in case it helped):
> > > 
> > > http://gluster.dogwind.com/files/statedump.voicemail.tar.gz
> > > 
> > > 
> > > What should I do?
> > > 
> > > Cheers,
> > > Kingsley.
> > > 
> > > _______________________________________________
> > > Gluster-users mailing list
> > > Gluster-users at gluster.org
> > > http://www.gluster.org/mailman/listinfo/gluster-users
> > > 
> > 
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://www.gluster.org/mailman/listinfo/gluster-users
> > 
>