Bug 1025425

Summary:	[RFE]: File grows beyond available size of brick
Product:	[Community] GlusterFS	Reporter:	Dean Bruhn <deanbruhn>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	atumball, bugs, hchiramm
Target Milestone:	---	Keywords:	RFE, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-10 12:30:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dean Bruhn 2013-10-31 16:30:32 UTC

Description of problem:
When a brick becomes full and a file is modified that causes the storage to report no space on the brick, the gluster volume will report a no space left on device.  

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


How reproducible:
Fill a brick on a  volume up, pick a file in that brick and add data to it so it will not longer fit in the full brick.

Steps to Reproduce:
1. fill brick
2. edit a file to cause it to no longer fit on the full brick
3. No space left on device error reported

Actual results:
No space error.

Expected results:
I would expect gluster to find space for the file on an alternate brick and move the data to that brick as part of the write process.

Additional info:

Comment 1 Amar Tumballi 2017-08-10 12:30:43 UTC

With Sharding this is not required. If we get into such scenario, we recommend sharding feature in general.

For now, other than sharding, we wouldn't be focusing on fixing this problem. Time to add more machine and call it a rebalance, to fix the problem in real world.