Bug 160319 - Enable O_DIRECT in dd
Enable O_DIRECT in dd
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
All Linux
medium Severity low
: ---
: ---
Assigned To: dff
dff
None
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-14 08:52 EDT by Stephen Tweedie
Modified: 2012-06-20 11:54 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 11:54:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Tweedie 2005-06-14 08:52:58 EDT
Description of problem:

Raw devices are deprecated.  The recommended way of achieving the same
functionality is to open a regular block device with O_DIRECT.

But customers cannot completely migrate to O_DIRECT as long as certain core
tools, often used on raw devices, do not support O_DIRECT.  In particular, dd is
often used to copy/backup raw device contents; it needs to support O_DIRECT to
enable this migration.  

The severity of lacking O_DIRECT is mitigated by the fact that buffered IO
_does_ still work; it's just less efficient, both in terms of CPU utilisation
and the load it places on the VM.
Comment 3 Jiri Pallich 2012-06-20 11:54:43 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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