Bug 1465931 - entry undergoing heal is not reflecting the action in heal info as "Possibly undergoing heal" or related
entry undergoing heal is not reflecting the action in heal info as "Possibly...
Status: CLOSED WONTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: disperse (Show other bugs)
3.3
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Ashish Pandey
nchilaka
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-28 09:11 EDT by nchilaka
Modified: 2017-08-21 07:17 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-21 07:17:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description nchilaka 2017-06-28 09:11:56 EDT
Description of problem:
====================
When a file is undergoing heal, the heal info doesn't show "Possibly undergoing heal" or "heal in progress" for such a file

Version-Release number of selected component (if applicable):
======
3.8.4-31



Steps to Reproduce:
1.create a 4+2 ec vol
2.keep writing to a big file 
3.kill one brick
4. after some time bring the brick online
5. trigger heal or wait for heal to pick up 


Actual results:
===========
when the file is undergoing heal the heal info doesnt show the status of this entry as undergoing heal

Expected results:
=================
the entry which is undergoing heal must reflect in the heal info details

Additional info:
Comment 2 nchilaka 2017-06-28 09:13:02 EDT
In my case I had only one big file 15GB which was undergoing heal , but the heal info doesn't say that the subject is under heal


[root@dhcp35-45 ~]# gluster v heal disperse info 
Brick 10.70.35.45:/rhs/brick1/disperse
/dir1/mv.3.tar 
Status: Connected
Number of entries: 1

Brick 10.70.35.130:/rhs/brick1/disperse
/dir1/mv.3.tar 
Status: Connected
Number of entries: 1

Brick 10.70.35.122:/rhs/brick1/disperse
/dir1/mv.3.tar 
Status: Connected
Number of entries: 1

Brick 10.70.35.23:/rhs/brick1/disperse
/dir1/mv.3.tar 
Status: Connected
Number of entries: 1

Brick 10.70.35.112:/rhs/brick1/disperse
/dir1/mv.3.tar 
Status: Connected
Number of entries: 1

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