3d9pjemc2s001@sneakemail.com
2002-Feb-23 09:35 UTC
Error help: ext3_new_block and ext3_free_blocks
After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: Feb 22 08:06:27 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block Feb 22 08:06:41 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 Feb 22 08:07:11 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 128 Feb 22 08:07:48 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 Feb 22 08:08:06 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 128 Feb 22 08:09:42 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 Feb 22 08:09:50 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 128 Feb 22 08:09:53 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 Feb 22 08:09:57 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 128 Feb 22 08:10:03 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 Feb 22 08:10:20 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block: Allocating block in system zone - block = 128 Never had one of these before. So I freaked out and rebooted to run fsck; this took quite a while, and detected lots of errors which I let the utility fix. After this run, I again rebooted, passed cleanly through the startup, and then these messages have begun appearing again in my logs. Any idea what's going on? I don't see any other messages about unreadable sectors or hints that there is a hardware problem, but I would believe you if you told me that my drive or motherboard is suspect. Harry ----------------------------------------------------- Protect yourself from spam, use http://sneakemail.com
On Sat, Feb 23, 2002 at 09:35:09AM -0000, 3d9pjemc2s001@sneakemail.com wrote:> After a bit of searching through these archives I haven't found quite my problem described yet, so let me bounce this off you guys: > > Red Hat 7.2, I run up2date whenever patches come out; right now I'm using kernel 2.4.9-21. > > Things have been quite pleasant for several months, but in the last week I have begun receiving the following error messages: > > Feb 22 08:06:27 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block > Feb 22 08:06:41 medmeta kernel: EXT3-fs error (device ide0(3,2)): ext3_free_blocks: Freeing blocks in system zones - Block = 128, count = 1 > > So I freaked out and rebooted to run fsck; this took quite a while, and detected lots of errors which I let the utility fix. After this run, I again rebooted, passed cleanly through the startup, and then these messages have begun appearing again in my logs. > > Any idea what's going on? I don't see any other messages about unreadable sectors or hints that there is a hardware problem, but I would believe you if you told me that my drive or motherboard is suspect.Yeah, it's probably random data corruption as opposed to unreadable sectors (which would indicate hard disk errors). I'd check the IDE disk cabling, and perhaps try backing off on the UDMA mode, and see if that helps. - Ted