Bug 709174 - Bug 615309 ext4 aio corruption on sparse files needs to be backported to RHEL 5
Summary: Bug 615309 ext4 aio corruption on sparse files needs to be backported to RHEL 5
Keywords:
Status: CLOSED DUPLICATE of bug 689830
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.6
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Eric Sandeen
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-30 23:47 UTC by John Zheng
Modified: 2011-05-31 21:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-31 16:16:39 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description John Zheng 2011-05-30 23:47:23 UTC 
Description of problem: Using aio on ext4 sparse files in RHEL 5.6 causes file corruption.


Version-Release number of selected component (if applicable): RHEL 5.6


How reproducible:Install XEN Guest on sparse file, and run /etc/cron.daily/prelink.  rpm -Va shows corruption


Steps to Reproduce:
1. Install RHEL 5.6 sparse diskguest on RHEL 5.6 host with ext4 formatted file system.  Do not do anything special partition alignment when configuring disks.
2. Check rpm -Va, should look good.  Perform I/O, specifically, run /etc/cron.daily/prelink
3. Check rpm -Va again after running prelink.  You can see the disk I/O from prelink results in binary file corruption.
  
Actual results:
Sparse files become corrupted.

Expected results:
No corruption on sparse files.

Additional info:This issue looks resolved according to technical notes tracking bug 615309 for RHEL 6.1 release.  But I can find no corresponding bug for RHEL 5.6, even though same issue exists there.  I can't seem to access bug  615309 content, is there a way for me to get access to that bug's content?
Comment 1 Eric Sandeen 2011-05-31 16:16:39 UTC 

*** This bug has been marked as a duplicate of bug 689830 ***
Comment 2 Eric Sandeen 2011-05-31 16:17:02 UTC 
There is a fix in the works for this in bug #689830
Comment 3 John Zheng 2011-05-31 20:51:51 UTC 
Will fix for #689830 make it into RHEL 5.7?

I don't have access to bug #689830 (or 615309).  How do I get access to see those bugs?
Comment 4 Eric Sandeen 2011-05-31 21:02:49 UTC 
Some bugs are filed by partners and are private by default.  Please check with your RHEL support to see about being added to cc: and then you can see it.  I do expect it to be in RHEL5.7 but again I would talk to your support folks about timing of fixes and releases.

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