Bug 1416467 - [RFE] Add support for posix_fallocate(3) call in fallocate(1) utility
Summary: [RFE] Add support for posix_fallocate(3) call in fallocate(1) utility
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: util-linux
Version: 7.5-Alt
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: Radka Skvarilova
URL:
Whiteboard:
Depends On:
Blocks: 1380361
TreeView+ depends on / blocked
 
Reported: 2017-01-25 15:07 UTC by Denis Chaplygin
Modified: 2017-08-01 21:43 UTC (History)
3 users (show)

Fixed In Version: util-linux-2.23.2-36.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 21:43:41 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2186 0 normal SHIPPED_LIVE util-linux bug fix and enhancement update 2017-08-01 18:41:36 UTC

Description Denis Chaplygin 2017-01-25 15:07:47 UTC
Description of problem: At the moment fallocate(1) utility uses fallocate(2) call to preallocate space to a file. That call fails if underlying filesystem, kernel or anything else doesn't support that functionality. On the other hand, posix_fallocate(3) have built-in fallback support and guarantees you, that space will always be preallocated. 

On the other hand, posix_fallocate(3) doesn't supports different preallocation modes, as fallocate(2) does.

It would be nice, if ability switch between different preallocation functions will be added, say with "--posix" key, so users will be able to select between more advanced fallocate(2) based implementation or more robust posix_fallocate(3) implementation.

Comment 8 errata-xmlrpc 2017-08-01 21:43:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2186


Note You need to log in before you can comment on or make changes to this bug.