Bug 1449167
Summary: | After selfheal of brick file size of few files differs | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | amudhan83 |
Component: | selfheal | Assignee: | Ashish Pandey <aspandey> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10 | CC: | aspandey, bugs, pkarampu |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-06-20 18:29:04 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
amudhan83
2017-05-09 10:56:18 UTC
Hi Amudhan, While the heal is going on you can see difference in "du -h" and "ls -h" That is ok. Reason - When heal starts, it truncate that file on a brick to size 0. If IO is going on, it will start form a specific offset and start write and that will become the size (offset + leanght) ls -l will give this size while du -h will give you the actual block size written on disk. It is not showing the zeros created because of truncate. Hi Ashish, heal is completed, but still its showing same. I think you have also mentioned that you have killed some heal process. 2. reading file from healing brick was slow. so, killed healing brick pid for user to download file. this was done twice in a days gap. That is the reason healing was not completed. However, it should have been started once you have all the bricks UP again. I would suggest to make sure that all the bricks are UP and then start heal. - See if this file is mentioned in heal info or not. If yes, just run index heal and this will be healed. - If NO, run client side heal using getfattr - If in doubt and you are seeing that file is not being healed even when all the bricks are UP, try full heal. If possible perform above steps while IO's are not going on that file. If still you are not able to heal the files, please give us xattrs of the file from all the brick, vol info and glustershd and mount logs. This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |