public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* ext3 fs corruption with 2.4.17
@ 2002-01-18 14:32 Christian Hammers
  2002-01-18 16:18 ` Matthias Andree
  2002-01-18 17:48 ` [Ext2-devel] " Andreas Dilger
  0 siblings, 2 replies; 4+ messages in thread
From: Christian Hammers @ 2002-01-18 14:32 UTC (permalink / raw)
  To: ext2-devel, linux-kernel

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?

On Thu, Jan 17, 2002 at 07:05:03PM +0100, root wrote:
> 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-

-- 
Christian Hammers    WESTEND GmbH - Aachen und Dueren     Tel 0241/701333-0
ch@westend.com     Internet & Security for Professionals    Fax 0241/911879
           WESTEND ist CISCO Systems Partner - Premium Certified


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ext3 fs corruption with 2.4.17
  2002-01-18 14:32 ext3 fs corruption with 2.4.17 Christian Hammers
@ 2002-01-18 16:18 ` Matthias Andree
  2002-01-18 17:48 ` [Ext2-devel] " Andreas Dilger
  1 sibling, 0 replies; 4+ messages in thread
From: Matthias Andree @ 2002-01-18 16:18 UTC (permalink / raw)
  To: linux-kernel

On Fri, 18 Jan 2002, Christian Hammers wrote:

> 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.

> > 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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Ext2-devel] ext3 fs corruption with 2.4.17
  2002-01-18 14:32 ext3 fs corruption with 2.4.17 Christian Hammers
  2002-01-18 16:18 ` Matthias Andree
@ 2002-01-18 17:48 ` Andreas Dilger
  2002-01-20 19:33   ` Roy Sigurd Karlsbakk
  1 sibling, 1 reply; 4+ messages in thread
From: Andreas Dilger @ 2002-01-18 17:48 UTC (permalink / raw)
  To: Christian Hammers; +Cc: ext2-devel, linux-kernel

On Jan 18, 2002  15:32 +0100, Christian Hammers wrote:
> 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?
> 
> On Thu, Jan 17, 2002 at 07:05:03PM +0100, root wrote:
> > 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/


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Ext2-devel] ext3 fs corruption with 2.4.17
  2002-01-18 17:48 ` [Ext2-devel] " Andreas Dilger
@ 2002-01-20 19:33   ` Roy Sigurd Karlsbakk
  0 siblings, 0 replies; 4+ messages in thread
From: Roy Sigurd Karlsbakk @ 2002-01-20 19:33 UTC (permalink / raw)
  To: Andreas Dilger; +Cc: Christian Hammers, ext2-devel, linux-kernel

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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-01-20 19:33 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-18 14:32 ext3 fs corruption with 2.4.17 Christian Hammers
2002-01-18 16:18 ` Matthias Andree
2002-01-18 17:48 ` [Ext2-devel] " Andreas Dilger
2002-01-20 19:33   ` Roy Sigurd Karlsbakk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox