Re: [Gluster-users] How to make sure self-heal backlog is empty ?
You can try kicking off a client side heal by running: ls -laR /your-gluster-mount/* Sometimes when I see just the GFID instead of the file name I have found that if I stat the file the name shows up in heal info. Before running that make sure that you don't have any split brain files: gluster v heal your-vol info split-brain If you do have split brain files follow: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/Recovering_from_File_Split-brain.html HTH! -b - Original Message - > From: "Hoggins!" <fucks...@wheres5.com> > To: "gluster-users" <gluster-users@gluster.org> > Sent: Tuesday, December 19, 2017 1:26:08 PM > Subject: [Gluster-users] How to make sure self-heal backlog is empty ? > > Hello list, > > I'm not sure what to look for here, not sure if what I'm seeing is the > actual "backlog" (that we need to make sure is empty while performing a > rolling upgrade before going to the next node), how can I tell, while > reading this, if it's okay to reboot / upgrade my next node in the pool ? > Here is what I do for checking : > > for i in `gluster volume list`; do gluster volume heal $i info; done > > And here is what I get : > > Brick ngluster-1.network.hoggins.fr:/export/brick/clem > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/clem > Status: Connected > Number of entries: 0 > > Brick ngluster-3.network.hoggins.fr:/export/brick/clem > Status: Connected > Number of entries: 0 > > Brick ngluster-1.network.hoggins.fr:/export/brick/mailer > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/mailer > Status: Connected > Number of entries: 0 > > Brick ngluster-3.network.hoggins.fr:/export/brick/mailer > > Status: Connected > Number of entries: 1 > > Brick ngluster-1.network.hoggins.fr:/export/brick/rom > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/rom > Status: Connected > Number of entries: 0 > > Brick ngluster-3.network.hoggins.fr:/export/brick/rom > > Status: Connected > Number of entries: 1 > > Brick ngluster-1.network.hoggins.fr:/export/brick/thedude > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/thedude > > Status: Connected > Number of entries: 1 > > Brick ngluster-3.network.hoggins.fr:/export/brick/thedude > Status: Connected > Number of entries: 0 > > Brick ngluster-1.network.hoggins.fr:/export/brick/web > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/web > > > > Status: Connected > Number of entries: 3 > > Brick ngluster-3.network.hoggins.fr:/export/brick/web > > > > > > > > > > > > Status: Connected > Number of entries: 11 > > > Should I be worrying with this never ending ? > > Thank you, > > Hoggins! > > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] How to make sure self-heal backlog is empty ?
Hi, Can you provide the - volume info - shd log - mount log of the volumes which are showing pending entries, to debug the issue. Thanks & Regards, Karthik On Wed, Dec 20, 2017 at 3:11 AM, Matt Waymack <mwaym...@nsgdv.com> wrote: > Mine also has a list of files that seemingly never heal. They are usually > isolated on my arbiter bricks, but not always. I would also like to find > an answer for this behavior. > > -Original Message- > From: gluster-users-boun...@gluster.org [mailto:gluster-users-bounces@ > gluster.org] On Behalf Of Hoggins! > Sent: Tuesday, December 19, 2017 12:26 PM > To: gluster-users <gluster-users@gluster.org> > Subject: [Gluster-users] How to make sure self-heal backlog is empty ? > > Hello list, > > I'm not sure what to look for here, not sure if what I'm seeing is the > actual "backlog" (that we need to make sure is empty while performing a > rolling upgrade before going to the next node), how can I tell, while > reading this, if it's okay to reboot / upgrade my next node in the pool ? > Here is what I do for checking : > > for i in `gluster volume list`; do gluster volume heal $i info; done > > And here is what I get : > > Brick ngluster-1.network.hoggins.fr:/export/brick/clem > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/clem > Status: Connected > Number of entries: 0 > > Brick ngluster-3.network.hoggins.fr:/export/brick/clem > Status: Connected > Number of entries: 0 > > Brick ngluster-1.network.hoggins.fr:/export/brick/mailer > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/mailer > Status: Connected > Number of entries: 0 > > Brick ngluster-3.network.hoggins.fr:/export/brick/mailer > > Status: Connected > Number of entries: 1 > > Brick ngluster-1.network.hoggins.fr:/export/brick/rom > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/rom > Status: Connected > Number of entries: 0 > > Brick ngluster-3.network.hoggins.fr:/export/brick/rom > > Status: Connected > Number of entries: 1 > > Brick ngluster-1.network.hoggins.fr:/export/brick/thedude > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/thedude > > Status: Connected > Number of entries: 1 > > Brick ngluster-3.network.hoggins.fr:/export/brick/thedude > Status: Connected > Number of entries: 0 > > Brick ngluster-1.network.hoggins.fr:/export/brick/web > Status: Connected > Number of entries: 0 > > Brick ngluster-2.network.hoggins.fr:/export/brick/web > > > > Status: Connected > Number of entries: 3 > > Brick ngluster-3.network.hoggins.fr:/export/brick/web > > > > > > > > > > > > Status: Connected > Number of entries: 11 > > > Should I be worrying with this never ending ? > > Thank you, > > Hoggins! > > ___ > Gluster-users mailing list > Gluster-users@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] How to make sure self-heal backlog is empty ?
Mine also has a list of files that seemingly never heal. They are usually isolated on my arbiter bricks, but not always. I would also like to find an answer for this behavior. -Original Message- From: gluster-users-boun...@gluster.org [mailto:gluster-users-boun...@gluster.org] On Behalf Of Hoggins! Sent: Tuesday, December 19, 2017 12:26 PM To: gluster-users <gluster-users@gluster.org> Subject: [Gluster-users] How to make sure self-heal backlog is empty ? Hello list, I'm not sure what to look for here, not sure if what I'm seeing is the actual "backlog" (that we need to make sure is empty while performing a rolling upgrade before going to the next node), how can I tell, while reading this, if it's okay to reboot / upgrade my next node in the pool ? Here is what I do for checking : for i in `gluster volume list`; do gluster volume heal $i info; done And here is what I get : Brick ngluster-1.network.hoggins.fr:/export/brick/clem Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/clem Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/clem Status: Connected Number of entries: 0 Brick ngluster-1.network.hoggins.fr:/export/brick/mailer Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/mailer Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/mailer Status: Connected Number of entries: 1 Brick ngluster-1.network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 1 Brick ngluster-1.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 1 Brick ngluster-3.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 0 Brick ngluster-1.network.hoggins.fr:/export/brick/web Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/web Status: Connected Number of entries: 3 Brick ngluster-3.network.hoggins.fr:/export/brick/web Status: Connected Number of entries: 11 Should I be worrying with this never ending ? Thank you, Hoggins! ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] How to make sure self-heal backlog is empty ?
Hello list, I'm not sure what to look for here, not sure if what I'm seeing is the actual "backlog" (that we need to make sure is empty while performing a rolling upgrade before going to the next node), how can I tell, while reading this, if it's okay to reboot / upgrade my next node in the pool ? Here is what I do for checking : for i in `gluster volume list`; do gluster volume heal $i info; done And here is what I get : Brick ngluster-1.network.hoggins.fr:/export/brick/clem Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/clem Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/clem Status: Connected Number of entries: 0 Brick ngluster-1.network.hoggins.fr:/export/brick/mailer Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/mailer Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/mailer Status: Connected Number of entries: 1 Brick ngluster-1.network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 0 Brick ngluster-3.network.hoggins.fr:/export/brick/rom Status: Connected Number of entries: 1 Brick ngluster-1.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 1 Brick ngluster-3.network.hoggins.fr:/export/brick/thedude Status: Connected Number of entries: 0 Brick ngluster-1.network.hoggins.fr:/export/brick/web Status: Connected Number of entries: 0 Brick ngluster-2.network.hoggins.fr:/export/brick/web Status: Connected Number of entries: 3 Brick ngluster-3.network.hoggins.fr:/export/brick/web Status: Connected Number of entries: 11 Should I be worrying with this never ending ? Thank you, Hoggins! signature.asc Description: OpenPGP digital signature ___ Gluster-users mailing list Gluster-users@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-users
