Bug 762965 (GLUSTER-1233)

Summary: Incorrect metadata self-heal behaviour
Product: [Community] GlusterFS Reporter: Anush Shetty <anush>
Component: replicateAssignee: Pavan Vilas Sondur <pavan>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: mainlineCC: gluster-bugs, shehjart, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anush Shetty 2010-07-27 08:28:50 UTC
This works properly when option metadata-change-log is set to 'on'. Hence closing this bug.

Comment 1 Shehjar Tikoo 2010-07-27 08:45:21 UTC
Wait a min, what if file size truncation happens the other way round? Thats meta-data.

Comment 2 Anush Shetty 2010-07-27 11:15:37 UTC
Metadata self-heal is happening only from server 1 to server 2 even if it supposed to be self-healing the other way. 

# touch dot
# ls -l dot 
-rw-r--r-- 1 root root 0 2010-07-27 16:42 dot

# kill server1
# chmod -R 777 dot 
# ls -l dot 
-rwxrwxrwx 1 root root 0 2010-07-27 16:42 dot

# server1 start
# find . | xargs stat > /dev/null
# ls -l dot 
-rw-r--r-- 1 root root 0 2010-07-27 16:42 dot

Comment 3 Vijay Bellur 2010-09-01 06:52:41 UTC
Needed option metadata-changelog on which is now on by default in mainline.