[Bug 16401] New: 2.6.35-r5 ext3 corruptions

[Bug 16401] New: 2.6.35-r5 ext3 corruptions

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=16401

           Summary: 2.6.35-r5 ext3 corruptions
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.35-rc5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext3
        AssignedTo: fs_ext3@kernel-bugs.osdl.org
        ReportedBy: maciej.rutecki@gmail.com
                CC: rjw@sisk.pl, maciej.rutecki@gmail.com,
                    david@fromorbit.com
        Regression: Yes


Subject    : 2.6.35-r5 ext3 corruptions
Submitter  : Dave Chinner <david@fromorbit.com>
Date       : 2010-07-15 10:57
Message-ID : 20100715105745.GI30737@dastard
References : http://marc.info/?l=linux-kernel&m=127919148825845&w=2

This entry is being used for tracking a regression from 2.6.34.  Please don't
close it until the problem is fixed in the mainline.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 16401] 2.6.35-r5 ext3 corruptions

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=16401


Maciej Rutecki <maciej.rutecki@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |16055




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 16401] 2.6.35-r5 ext3 corruptions

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=16401





--- Comment #1 from Dave Chinner <david@fromorbit.com>  2010-07-19 23:41:54 ---
The problem appears to have been specific to a single filesystem that was
corrupted in some way that e2fsck did not detect. e2fsck would report the fs as
clean (even with a forced check) but the problem would come back, always on
inodes around the 211,000 number.

The filesystem eventually trashed itself, but I made a fat-fingered mistake and
backed up the wrong image whenthe problem first manifested. Hence I can't
reproduce the problem now because I had to re-image the root drive.

>From this, I'd say this is not a regression, so closing this bug is fine by
me...

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 16401] 2.6.35-r5 ext3 corruptions

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=16401


Rafael J. Wysocki <rjw@sisk.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #2 from Rafael J. Wysocki <rjw@sisk.pl>  2010-07-20 15:18:06 ---
Closing, then.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

[Bug 16401] 2.6.35-r5 ext3 corruptions

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=16401


Rafael J. Wysocki <rjw@sisk.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED




-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.