Bug 912239

Summary: "gluster volume heal volname info" shows files which are under modification and may not require self-heal.
Product: [Community] GlusterFS Reporter: vsomyaju
Component: replicateAssignee: Nagaprasad Sathyanarayana <nsathyan>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: gluster-bugs, joe, nsathyan, pkarampu, ppquant, smohan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 15:40:20 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 vsomyaju 2013-02-18 08:08:59 UTC
Description of problem:
For a replicate volume, if file writes are going on at the backend, and at the same time "gluster volume heal volumename info" command is executed, it will show those files also because their entries are included in the xattrop directory. But those files do not require self heal.



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


How reproducible:
Always

Steps to Reproduce:
1. create replicate volume with two bricks (brick1 and brick2).
2. start volume
3. mount volume
4. execute dd if=/dev/random of=/$M0/file1 bs-1024 count=1000000 & 
   NOTE-- create large file at the mount point in background mode.
5 execute gluster volume heal volumename info command
  
Actual results:
It will show the file which is currenly under modification but it will mislead
too as the command is intended to show files which require self heal

Expected results:
Files which are under modification will be having extra message [ fiename is currently under modification] so that we can ensure that those files may not 
require self heal.

Additional info:

Comment 1 Joe Julian 2014-02-11 17:24:21 UTC
Why is this still in POST? The patch wasn't completed and hasn't been merged. Please finish fixing this.

Comment 2 Pranith Kumar K 2014-07-13 07:48:08 UTC
Fixed in 3.5.1

Comment 5 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.

Comment 6 Red Hat Bugzilla 2023-09-14 01:41:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days