Bug 1465931
Summary: | entry undergoing heal is not reflecting the action in heal info as "Possibly undergoing heal" or related | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Nag Pavan Chilakam <nchilaka> |
Component: | disperse | Assignee: | Ashish Pandey <aspandey> |
Status: | CLOSED WONTFIX | QA Contact: | Nag Pavan Chilakam <nchilaka> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.3 | CC: | rhs-bugs, storage-qa-internal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-21 11:17:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nag Pavan Chilakam
2017-06-28 13:11:56 UTC
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 |