Bug 1389532

Summary:	[RFE] Add a feature to fallocate after ftruncate
Product:	[Community] GlusterFS	Reporter:	Joe Julian <joe>
Component:	posix	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, pkarampu, ravishankar, rgowdapp, rhbugzilla, vbellur
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-19 05:19:31 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 Joe Julian 2016-10-27 20:07:57 UTC

Oversubscription of storage may not be desirable. Having users create 6 20TB images on a 60TB brick is a disaster waiting to happen. Yes, sharding may help mitigate that, but it would be nice to have allocation guarantees.

It seems to me that if you added an option to the posix translator where any ftruncate would immediately be followed with an fallocate for that same size, that guarantee could be met.

Comment 1 Vijay Bellur 2018-11-19 05:30:44 UTC

Migrated to github:

https://github.com/gluster/glusterfs/issues/577

Please follow the github issue for further updates on this bug.