ext3 fs corruption with 2.4.17
Hi
Again problems with my filesystems (probably a mainboard/cpu problem). It is (^H^H^H was) a quite new ext3 fs that was created with 2.4.17 and the very latest (stable) e2fsprogs and journalling. The device 8,7 was /var so the most used partition for write activity, read activity was mainly under /usr/local).
The filesystem was still usable but every write attempt lead to absolutely nonsense entries so I unmounted and fsck'ed it with quite good success.
Does anybody knows what exactly this means and if it could be helpful to track down the origin of the problems? Or did anybody else experienced this messages before?
Quoted 3 lines · root
Jan 17 19:01:15 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931009 Jan 17 19:01:16 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931018 Jan 17 19:01:16 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931019
[repeats several hundert times with increasing block numbers]
bye,
-christian-
Signature · 3 lines
Christian Hammers WESTEND GmbH - Aachen und Dueren Tel 0241/701333-0 [email protected] Internet & Security for Professionals Fax 0241/911879 WESTEND ist CISCO Systems Partner - Premium Certified
Quoted 5 lines · Christian Hammers
Again problems with my filesystems (probably a mainboard/cpu problem). It is (^H^H^H was) a quite new ext3 fs that was created with 2.4.17 and the very latest (stable) e2fsprogs and journalling. The device 8,7 was /var so the most used partition for write activity, read activity was mainly under
/usr/local).
Are you sure it's not your memory? Run memtest86; I recently had a box screw up its filesystems because the DIMM went bad.
Quoted 2 lines
Quoted 1 line
Jan 17 19:01:16 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931019[repeats several hundert times with increasing block numbers]
And that's what I got.
Quoted 9 lines · Christian Hammers
Does anybody knows what exactly this means and if it could be helpful to track down the origin of the problems? Or did anybody else experienced this messages before?
Quoted 3 lines · root
Jan 17 19:01:15 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931009 Jan 17 19:01:16 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931018 Jan 17 19:01:16 HOSTNAME kernel: EXT3-fs error (device sd(8,7)): ext3_new_block: Allocating block in system zone - block = 5931019[repeats several hundert times with increasing block numbers]
It means your block bitmap is corrupt and it says that metadata blocks are not in use, when they really are. That will lead to serious corruption.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
hi
I keep getting the exact same error
EXT3-fs error (device ide2(33,0)): ext3_new_block: Allocating block in system zone - block = 884763 EXT3-fs error (device ide2(33,0)): ext3_new_block: Allocating block in system zone - block = 884764 EXT3-fs error (device ide2(33,0)): ext3_new_block: Allocating block in system zone - block = 884765 EXT3-fs error (device ide2(33,0)): ext3_new_block: Allocating block in system zone - block = 884766 EXT3-fs error (device ide2(33,0)): ext3_new_block: Allocating block in system zone - block = 884767
...
The fs is newly created, and the computer has been working fine all the time.
Anyone know what this is ?
I'm running 2.4.17-tux-ide-rmap11c
roy
--
Roy Sigurd Karlsbakk, MCSE, MCNE, CLS, LCA
Computers are like air conditioners.
They stop working when you open Windows.