Hi, I'm running Debian lenny with linux-image-2.6.26-1-amd64 (deb
2.6.26-11). I have a lvm stripe over three sata disks (3.5TB total)
that is shared over NFS, and I getting following errors
EXT4-fs error (device dm-0): ext4_ext_search_right: bad header in inode #269200: unexpected eh_depth - magic f30a,entries 18, max 340(0), depth 1(2)
An user is having errors in concatenating large files (100+GB): basicly seems that the the resulting file is right size
and ends with right data, but anyway he gets following error:
cat: write error: Input/output error
on system that has imported partition over NFS. I'm not sure if the file he was accessing did had the same inode.
And once I got BUG below. I cannot right now upgrade system as there are some long-running analysis running,
but can do some tests at some point, and upgrade in few days.
# dumpe2fs /dev/work/wdata
dumpe2fs 1.41.3 (12-Oct-2008)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: 05867e70-54e2-48bf-8c67-5439e98c5982
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 test_filesystem
Default mount options: (none)
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 917536
Block count: 939525120
Reserved block count: 46976256
Free blocks: 507628950
Free inodes: 619199
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 799
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 32
Inode blocks per group: 2
Flex block group size: 16
Filesystem created: Thu Dec 11 10:36:48 2008
Last mount time: Mon Jan 26 13:05:07 2009
Last write time: Sat Jan 31 19:53:25 2009
Mount count: 1
Maximum mount count: 26
Last checked: Mon Jan 26 12:53:17 2009
Check interval: 15552000 (6 months)
Next check after: Sat Jul 25 13:53:17 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: 2714a303-cb2a-4bbc-8159-29bf52c617ca
Journal backup: inode blocks
Journal size: 128M
(rest of dumpe2fs output omitted: 32MiB, can put it available somewhere).
t. Markus
_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
02-04-2009, 02:55 PM
Theodore Tso
ext4 and unexpected eh_depth
On Wed, Feb 04, 2009 at 10:41:32AM +0200, Markus Peuhkuri wrote:
> Hi, I'm running Debian lenny with linux-image-2.6.26-1-amd64 (deb
> 2.6.26-11). I have a lvm stripe over three sata disks (3.5TB total)
> that is shared over NFS, and I getting following errors
>
> EXT4-fs error (device dm-0): ext4_ext_search_right: bad header in inode #269200: unexpected eh_depth - magic f30a,entries 18, max 340(0), depth 1(2)
I can't recall the patch which fixed this, but I'm 95% certain we've
seen this before, and it's been fixed since 2.6.26; I think in 2.6.27
or 2.6.28. Note that there have been a *huge* number of bug fixes for
ext4 since 2.6.26 and 2.6.27. If you must use such an old kernel I'd
suggest moving to at least 2.6.27.x or 2.6.28.x after Greg pulls in
the latest set of bug fixes. Critical bug fixes are still being back
ported to 2.6.27.x, although you won't see various performance
improvements unless you track a much newer kernel. I'd suggest at
least 2.6.28.y at this point.
- Ted
_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users
03-09-2009, 08:15 PM
Eric Sandeen
ext4 and unexpected eh_depth
Markus Peuhkuri wrote:
> Hi, I'm running Debian lenny with linux-image-2.6.26-1-amd64 (deb
> 2.6.26-11). I have a lvm stripe over three sata disks (3.5TB total)
> that is shared over NFS, and I getting following errors
>
> EXT4-fs error (device dm-0): ext4_ext_search_right: bad header in inode #269200: unexpected eh_depth - magic f30a,entries 18, max 340(0), depth 1(2)
>
> An user is having errors in concatenating large files (100+GB): basicly seems that the the resulting file is right size
> and ends with right data, but anyway he gets following error:
> cat: write error: Input/output error
> on system that has imported partition over NFS. I'm not sure if the file he was accessing did had the same inode.
ext4 and unexpected eh_depth
