Bug 762965 (GLUSTER-1233) - Incorrect metadata self-heal behaviour
Summary: Incorrect metadata self-heal behaviour
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-1233
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Pavan Vilas Sondur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-27 11:15 UTC by Anush Shetty
Modified: 2010-09-01 09:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.