mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Christian Hammers <ch@westend.com>
Cc: ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] ext3 fs corruption with 2.4.17
Date: Fri, 18 Jan 2002 10:48:46 -0700	[thread overview]
Message-ID: <20020118104846.Q29178@lynx.adilger.int> (raw)
In-Reply-To: <20020118143214.GH28471@westend.com>
In-Reply-To: <20020118143214.GH28471@westend.com>; from ch@westend.com on Fri, Jan 18, 2002 at 03:32:14PM +0100

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/


  parent reply	other threads:[~2002-01-18 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18 14:32 Christian Hammers
2002-01-18 16:18 ` Matthias Andree
2002-01-18 17:48 ` Andreas Dilger [this message]
2002-01-20 19:33   ` [Ext2-devel] " Roy Sigurd Karlsbakk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020118104846.Q29178@lynx.adilger.int \
    --to=adilger@turbolabs.com \
    --cc=ch@westend.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®