[Bugs] [Bug 1340032] New: Files not able to heal after arbiter and data bricks were rebooted

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1340032

            Bug ID: 1340032
           Summary: Files not able to heal after arbiter and data bricks
                    were rebooted
           Product: GlusterFS
           Version: mainline
         Component: arbiter
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: ksandha at redhat.com
                CC: bugs at gluster.org



Description of problem:
created script for 50 files 5mb each and during the creation rebooted 2 nodes
arbiter and data brick. while one brick was alive.

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


How reproducible:
1 time

Steps to Reproduce:
1.create a 1x3 volume -core(name) 
2. mounted on the client using fuse  at /mnt/core
3. ran this Script for 1 min.
for (( i=1;i<=50;i++ )) 
do 
dd if=/dev/urandom of=corefile$i bs=5M count=5 status=progress
done

4. rebooted the arbiter and one the data brick.
5. files 15 to 26 were only touched. No data was written. 0 byte file.
6. Files from arbiter and data weren't able to heal

[root at dhcp43-192 core]# gluster volume heal core info
Brick dhcp43-157.lab.eng.blr.redhat.com:/rhs/brick1/core
Status: Connected
Number of entries: 0

Brick dhcp43-192.lab.eng.blr.redhat.com:/rhs/brick1/core
/corefile16 
/corefile17 
/corefile18 
/corefile19 
/corefile20 
/corefile21 
/corefile22 
/corefile23 
/corefile24 
/corefile25 
/corefile26 
Status: Connected
Number of entries: 11

Brick dhcp43-153.lab.eng.blr.redhat.com:/rhs/brick1/core
/corefile16 
/corefile17 
/corefile18 
/corefile19 
/corefile20 
/corefile21 
/corefile22 
/corefile23 
/corefile24 
/corefile25 
/corefile26 
Status: Connected
Number of entries: 11



Actual results:
The files should weren't healed.

Expected results:
The files should have been healed.

Additional info:
logs kept at rhsqe-repo.lab.eng.blr.redhat.com:/var/www/html/sosreports/<bug>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.