Bug 1266357 - Distributed Disperse volume random file list error in client after adding new bricks
Distributed Disperse volume random file list error in client after adding new...
Product: GlusterFS
Classification: Community
Component: disperse (Show other bugs)
Unspecified Linux
unspecified Severity high
: ---
: ---
Assigned To: Shyamsundar
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-09-25 02:14 EDT by amudhan83
Modified: 2015-12-29 03:40 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-29 03:40:01 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log from client point (114.11 KB, text/plain)
2015-09-25 02:14 EDT, amudhan83
no flags Details

  None (edit)
Description amudhan83 2015-09-25 02:14:21 EDT
Created attachment 1076872 [details]
log from client point

Description of problem:
when new bricks added to a existing running cluster, client1 (fuse) not able to list file and log throws error but same file able to list after remount  and now again some other file is not listing. 

but able to list files in another client2 (fuse) when client1 is not bale to list file.

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

How reproducible:

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.


in child folder create 10 files

in existing cluster add new bricks.

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

but don't start rebalance or fix-layout now.

also ensure in existing brick usage in cluster are above 80% so data will start to move to new bricks.

start a transfering data to volume, now files will be written to newly added bricks.
now read files from any of the chil folders it would be missing.

Actual results:

randomly files are not listing

Expected results:

show list files without any issue

Additional info:
Comment 1 Backer 2015-09-26 02:33:23 EDT
Version-Release number of selected component (if applicable):
Comment 2 Backer 2015-09-29 08:46:56 EDT
This issue is resolved after changing the ulimit -n value from 1024 to 4096. If the brick count is more than 1024, we need to modify the ulimit -n value on clients as well as cluster nodes. So we can close this ticket.
Comment 3 Pranith Kumar K 2015-12-29 03:40:01 EST
Closing as per comment-2

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