Description of problem:
Suppose glustershd which is crawling over the list of entries to be self-healed finds that the entry which is to be self-healed is not found, then it is logging the message as an error. Its a valid case when 2 glustershds are crawling simulataneously and one of the glustershd already removed the entry as part of self-heal or the client process itself has removed the entry as part of the self-heal when lookup happened.

[2012-06-26 06:26:21.043576] I [afr-self-heald.c:282:_remove_stale_index] 0-master-replicate-0: Removing stale index for 3e052e29-1611-45a4-aaff-40dd95f77539 on master-client-1
[2012-06-26 06:26:21.043910] W [client3_1-fops.c:592:client3_1_unlink_cbk] 0-master-client-1: remote operation failed: No such file or directory
[2012-06-26 06:26:21.043936] E [afr-self-heald.c:287:_remove_stale_index] 0-master-replicate-0: 3e052e29-1611-45a4-aaff-40dd95f77539: Failed to remove index on master-client-1 - No such file or directory

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: