diff options
author | Filipe David Manana <[email protected]> | 2010-12-28 10:57:04 +0000 |
---|---|---|
committer | Björn-Egil Dahlberg <[email protected]> | 2013-01-09 18:15:02 +0100 |
commit | c48348233c467f7dc96728a31710abbb12cbe1f1 (patch) | |
tree | 61799089ba9052042ead12755a36b5bb818884ba /bootstrap | |
parent | 9229901660ef1c163ea82c76ea3dc21f5a4f83d4 (diff) | |
download | otp-c48348233c467f7dc96728a31710abbb12cbe1f1.tar.gz otp-c48348233c467f7dc96728a31710abbb12cbe1f1.tar.bz2 otp-c48348233c467f7dc96728a31710abbb12cbe1f1.zip |
Add file:allocate/3 operation
This operation allows pre-allocation of space for files.
It succeeds only on systems that support such operation.
The POSIX standard defines the optional system call
posix_fallocate() to implement this feature. However,
some systems implement more specific functions to
accomplish the same operation.
On Linux, if the more specific function fallocate() is
implemented, it is used instead of posix_fallocate(),
falling back to posix_fallocate() if the fallocate()
call failed (it's only supported for the ext4, ocfs2,
xfs and btrfs file systems at the moment).
On Mac OS X it uses the specific fcntl() operation
F_PREALLOCATE, falling back to posix_fallocate() if
it's available (at the moment Mac OS X doesn't provide
posix_fallocate()).
On any other UNIX system, it uses posix_fallocate() if it's
available. Any other system not providing this system call
or any function to pre-allocate space for files, this operation
always fails with the ENOTSUP POSIX error.
Diffstat (limited to 'bootstrap')
0 files changed, 0 insertions, 0 deletions