[Bugs] [Bug 1163760] New: when replace one brick on disperse volume, ls sometimes goes wrong

[bugzilla at redhat.com]

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

            Bug ID: 1163760
           Summary: when replace one brick on disperse volume, ls
                    sometimes goes wrong
           Product: GlusterFS
           Version: mainline
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: xhernandez at datalab.es
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    lidi at perabytes.com, lmohanty at redhat.com,
                    xhernandez at datalab.es



+++ This bug was initially created as a clone of Bug #1159498 +++

Steps to Reproduce:
1.gluster vol create test disperse 3 redundancy 1 10.10.21.20:/sdb
10.10.21.21:/sdb 10.10.21.22:/sdb force;
2.start the volume and mount it on /cluster2/test
3.cd /cluster2/test
4.mkdir a b c
5.touch a/1 b/2 c/3
6.gluster vol replace-brick test 10.10.21.22:/sdb 10.10.21.23:/sdb commit force
7.execute 'ls /cluster2/test/a' multiple times


Actual results:
sometimes 'ls /cluster2/test/a' can not list the file 1

--- Additional comment from Xavier Hernandez on 2014-11-04 13:39:51 CET ---

Are you using 3.6.0beta3 ? if that's the case, this problem should already be
solved in latest version (see bug #1149727)

--- Additional comment from lidi on 2014-11-05 03:07:29 CET ---

I use official 3.6.0 for this test.

--- Additional comment from Xavier Hernandez on 2014-11-10 16:43:11 CET ---

I've tried to reproduce this bug repeating your steps using version 3.6.0 and
I'm not able to see this problem. There was a bug on 3.6.0beta3 that caused
this problem, but it should be solved.

Can you reproduce this problem with a 3.6.0 and a newly created volume using
this version ?

--- Additional comment from lidi on 2014-11-11 04:43:19 CET ---

I got the source code form
git://forge.gluster.org/glusterfs-core/glusterfs.git,and branch is release-3.6

I reformat all the disks, create a new volume and test again.

Then I found I made a mistake on  previous description. 

The step 7 should be : "ls a" multiple times;"cd a"; "ls" multiple times,then
you'll see what I described.

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