Bug 1389532 - [RFE] Add a feature to fallocate after ftruncate
Summary: [RFE] Add a feature to fallocate after ftruncate
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: posix
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 20:07 UTC by Joe Julian
Modified: 2018-11-19 05:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:19:31 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

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


Links
System ID Private Priority Status Summary Last Updated
Github 577 0 None None None 2018-11-19 05:30:44 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.