Created attachment 615457[details]
glustershd.log file.
Description of problem:
------------------------
In a replicate volume , When there are files to be self-heal when a offline brick comes online, the glustershd.log file doesn't report any log messages on start of crawl and end of crawl.
Currently Available options for checking files to be self-healed:-
----------------------------------------------------------------
Number of files that has to be self-healed can be obtained from the gluster cli command : "gluster volume heal <vol_name> info"
Number of files that got self-healed (Only 1023 entries reported)can be obtained from the gluster cli command : "gluster volume heal <vol_name> info healed"
To check pending self-heals other option is to keep monitoring ".glusterfs/indices/xattrop" directory of the source brick.
Expected Output:-
------------------
We would like to see the start time of the crawl and End time of the crawl in the glustershd.log file. It would be helpful if number of files that got self-healed (only the count) is also reported in the glustershd.log file.
Version-Release number of selected component (if applicable):
------------------------------------------------------------
glusterfs 3.3.0rhs built on Sep 10 2012 00:49:11
(glusterfs-3.3.0rhs-28.el6rhs.x86_64)
Steps to Reproduce:
--------------------
1.Create a replicate volume (1x2). Start the volume
2.Bring down brick2
3.Create a fuse mount. Create 10k of files and directories from the mount point.
4.Bring back brick2 online
5.Check glustershd.log file for self-heal information.
Actual Result:-
---------------
No messages related to start of crawl, end of crawl is reported.
In the bz scrum, it was agreed to log the start and end of crawl immediately and this bug will be kept open for furture to log the number of files that got self healed.
*** Bug 868107 has been marked as a duplicate of this bug. ***
Comment 5krishnan parthasarathi
2013-09-23 06:23:18 UTC
vsomyaju,
Could you add a comment with the review url for the patch(es) which fix this issue? I am moving the bug state to ASSIGNED. The necessary criteria for a bug to be in POST state is that patches that fix the bug needs to be merged into upstream master branch. Once you have added the review url and a summary of the root cause, you could move the bug to POST state.
Created attachment 615457 [details] glustershd.log file. Description of problem: ------------------------ In a replicate volume , When there are files to be self-heal when a offline brick comes online, the glustershd.log file doesn't report any log messages on start of crawl and end of crawl. Currently Available options for checking files to be self-healed:- ---------------------------------------------------------------- Number of files that has to be self-healed can be obtained from the gluster cli command : "gluster volume heal <vol_name> info" Number of files that got self-healed (Only 1023 entries reported)can be obtained from the gluster cli command : "gluster volume heal <vol_name> info healed" To check pending self-heals other option is to keep monitoring ".glusterfs/indices/xattrop" directory of the source brick. Expected Output:- ------------------ We would like to see the start time of the crawl and End time of the crawl in the glustershd.log file. It would be helpful if number of files that got self-healed (only the count) is also reported in the glustershd.log file. Version-Release number of selected component (if applicable): ------------------------------------------------------------ glusterfs 3.3.0rhs built on Sep 10 2012 00:49:11 (glusterfs-3.3.0rhs-28.el6rhs.x86_64) Steps to Reproduce: -------------------- 1.Create a replicate volume (1x2). Start the volume 2.Bring down brick2 3.Create a fuse mount. Create 10k of files and directories from the mount point. 4.Bring back brick2 online 5.Check glustershd.log file for self-heal information. Actual Result:- --------------- No messages related to start of crawl, end of crawl is reported.