On Wed, Feb 18, 2004 at 11:55:50AM -0300, Leandro GuimarÃes Faria Corsetti Dutra wrote: > On Wed, 07 Jan 2004 12:53:26 -0800, Steven Ihde wrote: > > > I get "Aborting journal on device dm-x" and associated errors about every > > week or two. This is on a 2.6.0 kernel, ext3 filesystem running on lvm > > over md raid5. > > I've found a similar situation, have any fix came forth? Funny you should bring it up now. When I posted back in January it was suggested that I verify my hardware/memory was OK and also try to reproduce the bug on 2.4.24. So, I ran burnBX/burnMMX for a couple days, turned up no problems, did memtest86 overnight, also no problems, and then I switched to 2.4.24. I ran 2.4.24 (plus dm-1.00.07 for lvm2) for about 25 days and had no problems. This seemed like reasonable evidence the problem doesn't exist (or takes longer to show up) in 2.4.24. So then I switched to 2.6.2 (that being the latest 2.6 kernel). After about six days uptime on 2.6.2, I started seeing the problem again. Can anyone suggest what the next step is? Here are the latest entries from my syslog (this is 2.6.2). As it usually does, this occurred early in the morning while the locatedb was being updated. Feb 14 06:12:44 hamachi kernel: EXT3-fs error (device dm-4): ext3_readdir: bad entry in directory #5160995: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 Feb 14 06:12:44 hamachi kernel: Aborting journal on device dm-4. Feb 14 06:12:45 hamachi kernel: ext3_abort called. Feb 14 06:12:45 hamachi kernel: EXT3-fs abort (device dm-4): ext3_journal_start: Detected aborted journal Feb 14 06:12:45 hamachi kernel: Remounting filesystem read-only Feb 14 06:13:56 hamachi kernel: EXT3-fs error (device dm-4) in start_transaction: Journal has aborted Feb 14 06:13:57 hamachi last message repeated 741 times Thanks, Steve - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
