[Bugs] [Bug 1266359] New: folder not listing after fix-layout

bugzilla at redhat.com bugzilla at redhat.com
Fri Sep 25 06:33:00 UTC 2015


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

            Bug ID: 1266359
           Summary: folder not listing after fix-layout
           Product: GlusterFS
           Version: 3.7.3
         Component: disperse
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: amudhan83 at gmail.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Created attachment 1076877
  --> https://bugzilla.redhat.com/attachment.cgi?id=1076877&action=edit
ls of root folder before and after running fix-layout

Description of problem:
Folder not listing after adding new bricks and starting rebalance fix-layout 

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


How reproducible:
Always

Steps to Reproduce:
1.20 node with each 36 bricks

2. create disperse vol with 8 + 2 adding node{1..10}:/brick1
node{1..10}:/brick2 likewise

3. create folder hierarchy like this.

/root1/subroot1/aaaa/{a..z}/par{1..500}/chil{1..3}
/root1/subroot1/bbbb/{a..z}/par{1..500}/chil{1..3}
/root1/subroot2/aaaa/{a..z}/par{1..500}/chil{1..3}
/root1/subroot2/bbbb/{a..z}/par{1..500}/chil{1..3}
/root2/aaaa/{a..z}/par{1..500}/chil{1..3}
/root3/aaaa/{a..z}/par{1..500}/chil{1..3}
/root3/bbbb/{a..z}/par{1..500}/chil{1..3}
/root3/bbbb/{a..z}/par{1..500}/chil{1..3}

in child folder create 10 files

ls -R to see all folders all listing 

in existing cluster add new bricks.

add brick node{21..30}:/brick1 node{21..30}:/brick2 likewise

start rebalance or fix-layout now.

ls -R to see all folders all listing (some will be missing)

Actual results:

random folders are not listing for some time

Expected results:

It should list all folder even when rebalance is running

Additional info:

starting fix-layout makes folders not availble till it completes, it takes a
day to list some folders.

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


More information about the Bugs mailing list