Bug 769560

Summary:	New stripe block size set is not taking effect
Product:	[Community] GlusterFS	Reporter:	shylesh <shmohan>
Component:	stripe	Assignee:	shishir gowda <sgowda>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	mainline	CC:	gluster-bugs, nsathyan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-22 06:17:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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