Hitting the same bug with 2.6.31-rc1 on s390 arch. EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in directory #2: rec_len % 4 != 0 - offset=44, inode=12, rec_len=139, name_len=10 __log_wait_for_space: needed 256 blocks and only had 0 space available __log_wait_for_space: no way to get more journal space ------------[ cut here ]------------ Badness at fs/jbd/checkpoint.c:164 Modules linked in: loop qeth_l3 autofs4 lockd sunrpc iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 qeth_l2 vmur qeth qdio ccwgroup dm_round_robin dm_multipath scsi_dh sd_mod scsi_mod multipath dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod dasd_fba_mod dasd_eckd_mod dasd_mod ext3 jbd CPU: 1 Not tainted 2.6.31-rc1 #2 Process fstest (pid: 3329, task: 0000000032054770, ksp: 0000000031e17870) Krnl PSW : 0704100180000000 000003e00004324c (__log_wait_for_space+0x150/0x19c [jbd]) R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:1 PM:0 EA:3 Krnl GPRS: 0000000000002d48 0000000001433000 000000000000003d 0400000000000001 000000000004aa66 00000000002f3ea8 0000000032574700 0000000000000000 000003e000000000 0000000000000100 0000000000000000 000000003e66a400 000003e00003d000 000003e000046580 000003e000043248 0000000031e17c20 Krnl Code: 000003e00004323c: c020000026eb larl %r2,3e000048012 000003e000043242: c0e5ffffcf05 brasl %r14,3e00003d04c 000003e000043248: a7f40001 brc 15,3e00004324a >000003e00004324c: a7390000 lghi %r3,0 000003e000043250: b904002b lgr %r2,%r11 000003e000043254: c0e500000ddc brasl %r14,3e000044e0c 000003e00004325a: 4120b024 la %r2,36(%r11) 000003e00004325e: c0e5ffffcf0b brasl %r14,3e00003d074 Call Trace: ([<000003e000043248>] __log_wait_for_space+0x14c/0x19c [jbd]) [<000003e00003dd94>] start_this_handle+0x384/0x3f8 [jbd] [<000003e0000401c2>] journal_start+0xce/0x10c [jbd] [<000003e0000a758a>] ext3_dirty_inode+0x42/0xac [ext3] [<000000000010d4b4>] __mark_inode_dirty+0x4c/0x140 [<0000000000103016>] touch_atime+0x162/0x174 [<00000000000fb6dc>] vfs_readdir+0xbc/0xe0 [<00000000000fb764>] SyS_getdents64+0x64/0xcc [<00000000000268ba>] sysc_tracego+0xe/0x14 [<000000498d96b890>] 0x498d96b890 Last Breaking-Event-Address: [<000003e000043248>] __log_wait_for_space+0x14c/0x19c [jbd] Aborting journal on device loop0. attempt to access beyond end of device loop0: rw=0, want=107522, limit=40960 ext3_abort called. EXT3-fs error (device loop0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device loop0): ext3_readdir: bad entry in directory #11: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1155, name_len=0 attempt to access beyond end of device loop0: rw=0, want=107522, limit=40960 attempt to access beyond end of device loop0: rw=0, want=107522, limit=40960 attempt to access beyond end of device loop0: rw=0, want=107522, limit=40960 EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in directory #2: rec_len % 4 != 0 - offset=44, inode=12, rec_len=139, name_len=10 EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in directory #2: rec_len % 4 != 0 - offset=44, inode=12, rec_len=139, name_len=10 EXT3-fs error (device loop0): ext3_readdir: bad entry in directory #11: rec_len % 4 != 0 - offset=0, inode=0, rec_len=1155, name_len=0 ext3_abort called. EXT3-fs error (device loop0): ext3_put_super: Couldn't clean up the journal Thanks and Regards R.Nageswara Sastry