Bug 662839 - [REG][4.9] Filesystem corruption happens on ext2 filesystem
Summary: [REG][4.9] Filesystem corruption happens on ext2 filesystem
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.9
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Alexander Viro
QA Contact: Petr Beňas
URL:
Whiteboard:
: 665521 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-14 03:11 UTC by Masayoshi Yamazaki
Modified: 2018-11-14 16:02 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-16 15:49:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0263 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 4.9 kernel security and bug fix update 2011-02-16 15:14:55 UTC

Comment 3 Eric Sandeen 2010-12-14 05:38:16 UTC 
Looks like a regression between 2.6.9-89.44.EL and 2.6.9-89.45.EL
 
[esandeen@neon rhel4]$ git log --pretty=oneline kernel-2_6_9-89_44_EL..kernel-2_6_9-89_45_EL
6087ca1c0491c7e462de50db97151d828849a569 spec file release and changelog update for 89.45.EL
7fc888ffac4b4acc622270c11aa568c3667a9053 scsi: scsi_do_req submitted commands (tape) never complete when device goes
d9d7622e237d99e53dfcd76ca987aac40a41669d scsi: log msg when getting unit attention
f8323470e6ef56184fb4241442dd394fafd72d6b jbd: fix panic in jbd when running bashmemory
3f2fb8911e1b21cd5ca979e1e8315633230edcd5 qla2xxx: work around hypertransport sync flood error on sun x4200 with qla2xxx
b6612982abf54577c74564aa7973cc5f4f5a9e46 aio: implement request batching for better merging and throughput
06f31e276650ba22ea5d446d2b9a125a660ee0ca fs: a bunch of patches to fix various nfsd/iget() races
1f17e336f00a050e6054dd3e42c393d21e3033d0 net: bonding: add debug module option
d3bdbd35dc1bcc099201cf7e650659e85ed85421 fix fd leaks if pipe() is called with an invalid address

I guess I'd lean towards blaming 06f31e276650ba22ea5d446d2b9a125a660ee0ca
but we can test that theory tomorrow...

-Eric
Comment 4 Eric Sandeen 2010-12-14 17:48:16 UTC 
I've confirmed that it's the change for bug #189918 which broke this; new inodes don't seem to be getting written to disk.
Comment 7 Alexander Viro 2010-12-24 00:08:49 UTC 
Fix posted...
Comment 8 RHEL Program Management 2011-01-03 17:49:45 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 14 Vivek Goyal 2011-01-19 17:50:45 UTC 
Committed in 97.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
Comment 18 Petr Beňas 2011-01-20 10:27:38 UTC 
Reproduced in 2.6.9-96.EL and verified in 2.6.9-97.EL.
Comment 21 Eric Sandeen 2011-02-15 21:58:23 UTC 
*** Bug 665521 has been marked as a duplicate of this bug. ***
Comment 22 errata-xmlrpc 2011-02-16 15:49:00 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0263.html
Note You need to log in before you can comment on or make changes to this bug.