Bug 795689

Summary: meta-data, data, entry, missing-entry, gfid, self-heal failed on files/dirs
Product: [Community] GlusterFS Reporter: Shwetha Panduranga <shwetha.h.panduranga>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED WORKSFORME QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, vbellur
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: 2012-04-02 05:40:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Attaching client log none

Description Shwetha Panduranga 2012-02-21 10:03:34 UTC
Created attachment 564626 [details]
Attaching client log

Description of problem:
Self-heal not happening on files/dirs. 

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

How reproducible:
often

Steps to Reproduce:
1.Create a replicate volume with 2 bricks (self-heal daemon is off)
2.Start the volume
3.Mount to volume from client
4.Create files and dirs.
5. Bring down one of the brick
6. Create files and dirs. change ownership/permissions/ on existing files
7. Bring back brick
8. find . | xargs stat

Actual results:
Self-heal of data, meta-data, gfid, failed.

Expected results:
Should self-heal the files/dirs. 

Additional info:
It's a regression.

Comment 1 Pranith Kumar K 2012-03-01 10:28:59 UTC
According to the logs one of the self-heal failed because of split-brain
other failed because of invalid argument in lookup. There is a separate bug for this. The other 2 failed because it could not take entrylks at that moment. I don't see any new bug according to the given information. Please let me know if I am missing something.

Comment 2 Shwetha Panduranga 2012-04-02 05:40:23 UTC
Self-heal of files/dirs are working fine now. Hence closing this bug.