The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Stephen Tweedie <sct@redhat.com>
To: Anton Altaparmakov <aia21@cantab.net>,
	sct@redhat.com, Andrew Morton <akpm@zip.com.au>,
	LKML <linux-kernel@vger.kernel.org>,
	ext3-users@redhat.com
Subject: Re: EXT3-fs error on kernel 2.4.18-pre3
Date: Thu, 4 Jul 2002 21:51:46 +0100	[thread overview]
Message-ID: <20020704215146.E27198@redhat.com> (raw)
In-Reply-To: <20020703202107.GA14654@clusterfs.com>; from adilger@turbolinux.com on Wed, Jul 03, 2002 at 02:21:07PM -0600

Hi,

On Wed, Jul 03, 2002 at 02:21:07PM -0600, Andreas Dilger
<adilger@turbolinux.com> wrote:

> On Jul 03, 2002  20:05 +0100, Anton Altaparmakov wrote:
> > I just noticed that my file server running 2.4.18-pre3 + IDE patches &
> > NTFS patches has this error message in the logs:
> > 
> > EXT3-fs error (device md(9,4)): ext3_free_blocks: Freeing blocks not in
> > datazone - block = 33554432, count = 1
> > 
> > This is the only ext3 error I have seen and the uptime is currently over
> > 74 days. The error actually appeared two weeks ago. The timing coincides
> > well with when this device (/dev/md4, a MD RAID-1 array) ran out of
> > space, so it may well be related.
> 
> This was fixed in newer kernels.

No, the out-of-space behaviour was either an ext3_error if we ran out
of inodes, or a minor i_nrblocks accounting error if we ran out of
disk blocks.

The bad pointer here is 0x2000000, and a bit flip like that is more
often an indicator of bad memory than anything else.

Cheers,
 Stephen

  reply	other threads:[~2002-07-04 22:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-03 19:05 EXT3-fs error on kernel 2.4.18-pre3 Anton Altaparmakov
2002-07-03 20:21 ` Andreas Dilger
2002-07-04 20:51   ` Stephen Tweedie [this message]
2002-07-04  9:55 ` Rogier Wolff

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=20020704215146.E27198@redhat.com \
    --to=sct@redhat.com \
    --cc=aia21@cantab.net \
    --cc=akpm@zip.com.au \
    --cc=ext3-users@redhat.com \
    --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