Bug 903258

Summary: Need description of FALLOC_FL_PUNCH_HOLE flag for fallocate(2) system call
Product: Red Hat Enterprise Linux 6 Reporter: Eryu Guan <eguan>
Component: man-pages-overridesAssignee: Peter Schiffer <pschiffe>
Status: CLOSED ERRATA QA Contact: Iveta Wiedermann <isenfeld>
Severity: low Docs Contact:
Priority: low    
Version: 6.4CC: isenfeld, mtk.manpages, ovasik, tlavigne
Target Milestone: rcKeywords: ManPageChange, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: missing description of FALLOC_FL_PUNCH_HOLE flag on fallocate(2) man page Consequence: incomplete documentation Fix: document FALLOC_FL_PUNCH_HOLE flag on fallocate(2) man page Result: complete documentation
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-21 22:55:13 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:
Bug Depends On:    
Bug Blocks: 1011198    
Attachments:
Description Flags
man-pages-3.22-fallocate.patch none

Description Eryu Guan 2013-01-23 15:28:46 UTC 
Description of problem:
punch hole support for ext4 has been added into rhel6.4 kernel via bug 739101, and it adds new flag FALLOC_FL_PUNCH_HOLE to fallocate(2)

Version-Release number of selected component (if applicable):
man-pages-3.22-20.el6
Comment 1 RHEL Program Management 2013-01-27 06:47:09 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 2 Michael Kerrisk 2013-02-12 23:19:43 UTC 
This has already been documented in upstream since man-pages-3.36.
Comment 3 Peter Schiffer 2013-09-20 16:09:26 UTC 
Created attachment 800562 [details]
man-pages-3.22-fallocate.patch
Comment 9 errata-xmlrpc 2013-11-21 22:55:13 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.

http://rhn.redhat.com/errata/RHBA-2013-1695.html