Bug 586813 - Force page cache to be sent in sequential order [NEEDINFO]
Summary: Force page cache to be sent in sequential order
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-28 12:19 UTC by Charlie Wyse
Modified: 2014-06-03 12:29 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-06-03 12:29:54 UTC
Target Upstream Version:
pm-rhel: needinfo? (cwyse)

Attachments (Terms of Use)

Description Charlie Wyse 2010-04-28 12:19:28 UTC
Description of problem:
When a system is receiving a lot of write data, say from NFS.  The pages are written out to disk in no particular order.  This can cause issues with some file systems.  The ability to force synchronization of pages written to disk would be helpful.

How reproducible:
Happsn with current VM configurations

Steps to Reproduce:
1. Setup a NFS server, then send a 8g file to it.
2. If you look at the code you will see several offsets as it places data anywhere in that 8g file in as it sees fit.
Actual results:
Data is written to disk out of order.

Expected results:
Some kind of option to force data to be sync'ed in memory before written.

Comment 1 RHEL Program Management 2014-03-07 12:52:05 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 2 RHEL Program Management 2014-06-03 12:29:54 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).

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