[Bug 337246] [NEW] kernel bug corrupts filesystem on heavy parallel I/O

[ddi]

Public bug reported:

Distro is Ubuntu Server 8.10, running kernel image is 2.6.27-9-server
smp on x86_64.

(Installed a couple months ago, never updated since the box does not
have internet access per default.)

On one box with particularly heavy database I/O, we're seeing this in
the system log:

==================
[1099257.456522] EXT4-fs error (device sdb1): ext4_ext_search_right: bad header in inode #2621457: unexpected eh_depth - magic f30a, entries 340, max 340(0), depth 1(2)
[1099257.495979] EXT4-fs error (device sdb1): ext4_ext_search_right: bad header in inode #2621457: unexpected eh_depth - magic f30a, entries 328, max 340(0), depth 1(2)
[1099257.505934] EXT4-fs error (device sdb1): ext4_ext_search_right: bad header in inode #2621457: unexpected eh_depth - magic f30a, entries 340, max 340(0), depth 1(2)
==================

... ad infinitum.

Sounds a lot like a problem reported against 2.6.23, see:
http://markmail.org/search/?q=ext4_ext_search_right+depth+%22bad+header+in+inode%22#query:ext4_ext_search_right%20depth%20%22bad%20header%20in%20inode%22+page:1+mid:cuek4hlduagxee5c+state:results

I couldn't locate if/when the discussed new-extent-function.patch was
merged into the mainline kernel, since git.kernel.org does not have a
search function and also specifically sets novisit for search engines
(via "User-agent: * Disallow: /" in robots.txt) such as Google.

Here's dumpe2fs for the filesystem:
===================
dumpe2fs 1.41.3 (12-Oct-2008)
Last mounted on:          <not available>
Filesystem UUID:          7adcc7a6-5dd4-4fd5-b988-c92f9429a06c
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean with errors
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              90177536
Block count:              360683091
Reserved block count:     18034154
Free blocks:              116980051
Free inodes:              90170042
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      938
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Tue Dec  2 17:23:58 2008
Last mount time:          Wed Feb 18 21:44:25 2009
Last write time:          Tue Mar  3 15:19:14 2009
Mount count:              5
Maximum mount count:      30
Last checked:             Tue Dec  2 17:23:58 2008
Check interval:           15552000 (6 months)
Next check after:         Sun May 31 18:23:58 2009
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      2180b9fc-09e3-445e-8170-302178b2eadd
Journal backup:           inode blocks
Journal size:             128M
========================

Has the bugfix in the above email been applied to the Ubuntu Server
kernel images?  If not, then that's probably the bottom of this issue.
*hope* ;-).

** Affects: linux-meta (Ubuntu)
     Importance: Undecided
         Status: New

-- 
kernel bug corrupts filesystem on heavy parallel I/O
https://bugs.launchpad.net/bugs/337246
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.