Bug 1721028 - gluster v heal <vol_name> info is stuck
Summary: gluster v heal <vol_name> info is stuck
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: disperse
Version: rhgs-3.5
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: RHGS 3.5.0
Assignee: Ashish Pandey
QA Contact: Upasana
URL:
Whiteboard:
Depends On:
Blocks: 1696809
TreeView+ depends on / blocked
 
Reported: 2019-06-17 07:36 UTC by Upasana
Modified: 2019-11-06 09:21 UTC (History)
7 users (show)

Fixed In Version: glusterfs-6.0-7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 12:21:54 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:22:31 UTC

Description Upasana 2019-06-17 07:36:35 UTC
Description of problem:
========================
gluster v heal <vol_name> info is stuck from the past 3 hours

Version-Release number of selected component (if applicable):
=============================================================
glusterfs-6.0-5.el7rhgs.x86_64

How reproducible:
================
1/1


Steps to Reproduce:
====================

Was trying to verify Bug 1716385 - [EC] volume heal info command stucks forever even if all bricks are running  and had created 10000 files and 10 directories
1.Created a 3X(4+2) EC volume 
2.Brought down 2 bricks from each subvol 
3.Created 10000 files and 10 directories
4.Started volume - Force
5.Gave gluster v heal <vol_name> info


Actual results:
===============
Heal info is hanging

Expected results:
=================
Heal info is hanging

Additional info:
================
Had done the exact same steps on a 3.4.4 setup and everything is fine there , even healing has completed


The setup is in the same state if anyone wants to debug , will ping the details.

Comment 15 Atin Mukherjee 2019-06-24 07:09:38 UTC
This looks to be a blocker. I am acking this bug right away, investigation can continue.

Comment 22 errata-xmlrpc 2019-10-30 12:21:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:3249


Note You need to log in before you can comment on or make changes to this bug.