Bug 765424 (GLUSTER-3692)

Summary: md5sum of the VM image files on bricks doesn't match after the self-heal completion on the image files.
Product: [Community] GlusterFS Reporter: Shwetha H Panduranga <shwetha>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED CURRENTRELEASE QA Contact: Shwetha Panduranga <shwetha.h.panduranga>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3-betaCC: gluster-bugs, jdarcy, ujjwala, vbellur, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 17:28:42 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
Brick1 Data
none
Brick2 Data none

Description Shwetha H Panduranga 2011-10-04 08:08:36 UTC
Link to the document capturing the output:https://docs.google.com/spreadsheet/ccc?key=0AlvBPsMsaL6edFlBX0xQY0dTUGZRU0FLaGlDUVFJcWc&hl=en_US#gid=1

Comment 1 Shwetha H Panduranga 2011-10-04 11:06:57 UTC
Set-up:- 
1) Create a Replicate Volume with count 2 on the Server
2) Start the replicate volume
3) Create a mount point /vm on the Dom0
4) Mount the replicate volume on /vm of the Dom0

Execution:-
Step1:-
-----
1) check the md5sum of the VM image file(GuestOS) on each brick
2) Check the extended attributes of the image file on each brick

The md5sum and extended attributes of the VM image file are same.

Step2:-
------
3) Start the Guest OS (VM)
4) Perform IO Operations
5) Bring down brick1 while IO operation is still in progress
6) Shutdown the Guest OS once the IO operation is complete
7) Calculate the md5sum of the VM image file(GUestOS) on live brick
8) Bring back the brick1
9) Self-heal automatically initiated (proactive self-heal on)
10) Self-heal successfully completed

Step3:-
------
11) Check the extended attributes of the image file on each brick

The extended attributes of the image file on each brick is same

Step4:-
-----
12) check the md5sum of the VM image file(GuestOS) on each brick

The MD5SUM of the VM image file doesn't match.

Comment 2 Shwetha H Panduranga 2011-10-05 06:47:33 UTC
Observed the failure on 3.3.0qa14. Updated the Google doc with the new data https://docs.google.com/spreadsheet/ccc?key=0AlvBPsMsaL6edFlBX0xQY0dTUGZRU0FLaGlDUVFJcWc&hl=en_GB#gid=2

Comment 3 Shwetha H Panduranga 2011-11-25 07:16:40 UTC
Created attachment 722

Comment 4 Shwetha H Panduranga 2011-11-25 07:17:15 UTC
Created attachment 723

Comment 5 Vijay Bellur 2012-02-24 07:45:19 UTC
Can you please reproduce this with 3.3.0qa24?

Comment 6 Pranith Kumar K 2012-04-01 03:39:58 UTC
I found that the self-heal of files with holes has a bug. I am suspecting this issue is the result of that. Could you confirm if the vm image type you are using has holes in it.

Pranith

Comment 7 Anand Avati 2012-04-04 23:22:45 UTC
CHANGE: http://review.gluster.com/3065 (cluster/afr: Handle self-heal of files with holes) merged in master by Anand Avati (avati)

Comment 8 Pranith Kumar K 2012-06-01 07:16:51 UTC
I havent experienced any md5mismatch issue after this fix. Closing the bug. Please feel free to re-open the bug if you find another way to hit this issue.

Comment 9 Shwetha Panduranga 2012-06-06 07:49:22 UTC
I will try to recreate this bug post 3.3 release. Hence moving it to Modified state.