EXT3 errors
Hi
Does anyone what cause's these message. I have a 41M messages file because of the.
Jul 1 04:02:14 localhost kernel: EXT3-fs error (device ide0(3,70)): ext3_new_block: Allocating block in system zone - block = 32802 Jul 1 04:02:14 localhost kernel: EXT3-fs error (device ide0(3,70)): ext3_new_block: Allocating block in system zone - block = 32803 Jul 1 04:02:14 localhost kernel: EXT3-fs error (device ide0(3,70)): ext3_new_block: Allocating block in system zone - block = 32804 Jul 1 04:02:15 localhost kernel: EXT3-fs error (device ide0(3,70)): ext3_free_blocks: Freeing blocks in system zones - Block = 32802, count = 3 Jul 1 04:06:02 localhost kernel: attempt to access beyond end of device Jul 1 04:06:02 localhost kernel: 03:46: rw=0, want=1025837100, limit=6345643 Jul 1 04:06:02 localhost kernel: EXT3-fs error (device ide0(3,70)): ext3_readdir: directory #17205 contains a hole at offset 0 Jul 1 04:06:02 localhost kernel: attempt to access beyond end of device Jul 1 04:06:02 localhost kernel: 03:46: rw=0, want=226335104, limit=6345643 Jul 1 04:06:02 localhost kernel: EXT3-fs error (device ide0(3,70)): ext3_readdir: directory #17205 contains a hole at offset 4096 Jul 1 04:06:02 localhost kernel: attempt to access beyond end of device Jul 1 04:06:02 localhost kernel: 03:46: rw=0, want=362922408, limit=6345643 Jul 1 04:06:02 localhost kernel: EXT3-fs error (device ide0(3,70)):
ext3_readdir: directory #17205 contains a hole at offset 8192
I was using linux-2.4.19-pre10-aa when I found these messages this morning.
Thanx
-- Bongani
Quoted 8 lines · Bongani
Hi
Does anyone what cause's these message. I have a 41M messages file because of the.
Jul 1 04:02:14 localhost kernel: EXT3-fs error (device ide0(3,70)):
ext3_new_block: Allocating block in system zone - block = 32802
Your filesystem is wrecked. Did you get some I/O errors?
You need to unmount it, run `e2fsck -f' and fix it up.
-
Quoted 11 lines · Andrew Morton
Quoted 8 lines · Bongani
Hi
Does anyone what cause's these message. I have a 41M messages file because of the.
Jul 1 04:02:14 localhost kernel: EXT3-fs error (device ide0(3,70)):
ext3_new_block: Allocating block in system zone - block = 32802Your filesystem is wrecked. Did you get some I/O errors?
I found these from the day before
Jun 30 12:31:00 localhost kernel: hdb: dma_intr: status=0x51 {DriveReady
SeekComplete Error }
Jun 30 12:31:00 localhost kernel: hdb: dma_intr: error=0x84{DriveStatusError BadCRC }
Quoted 3 lines
You need to unmount it, run `e2fsck -f' and fix it up.
I have done that already
Thank you
Quoted 4 lines · Bongani
Quoted 3 lines · Andrew Morton
Quoted 2 lines · Bongani
Jul 1 04:02:14 localhost kernel: EXT3-fs error (device ide0(3,70)):
ext3_new_block: Allocating block in system zone - block = 32802
Quoted 8 lines
Quoted 1 line
Your filesystem is wrecked. Did you get some I/O errors?
I found these from the day before
Jun 30 12:31:00 localhost kernel: hdb: dma_intr: status=0x51 {DriveReady SeekComplete Error } Jun 30 12:31:00 localhost kernel: hdb: dma_intr: error=0x84{DriveStatusError BadCRC }
Ah, so you hard disk is wrecked too...
See what badblocks -v on the damaged partition device has to say...
-K.