Bug 769560 - New stripe block size set is not taking effect
Summary: New stripe block size set is not taking effect
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: stripe
Version: mainline
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: shishir gowda
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-21 10:44 UTC by shylesh
Modified: 2013-12-09 01:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-22 06:17:40 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description shylesh 2011-12-21 10:44:21 UTC 
Description of problem:
Stripe block size changed through volume set is not reflected

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

How reproducible:


Steps to Reproduce:
1.create a stripe volume (default blocksize 128KB)
2.create some files and observer the size extended attribute for these files on backend
3. execute the command "gluste volume set $vol cluster.stripe-block-size 2M
4. Now create some file on mount point and observe the extended attribs for these files on the backend  

Actual results:
block size will be still 128KB

Expected results:
block size should have changed to new value

Additional info:
Comment 1 shishir gowda 2011-12-22 06:17:40 UTC 
Please check when passing the right argument of 2MB (not 2M).
Marking it as invalid
Note You need to log in before you can comment on or make changes to this bug.