public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bongani <bonganilinux@mweb.co.za>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXT3 errors
Date: 02 Jul 2002 06:15:40 +0200	[thread overview]
Message-ID: <1025583346.3267.7.camel@localhost.localdomain> (raw)
In-Reply-To: <3D20CBD7.BC184F53@zip.com.au>

On Mon, 2002-07-01 at 23:38, Andrew Morton wrote:
> Bongani wrote:
> > 
> > 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?
 
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 }


> 
> You need to unmount it, run `e2fsck -f' and fix it up.
>

I have done that already

Thank you



  reply	other threads:[~2002-07-02  4:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 19:24 EXT3 errors Bongani
2002-07-01 21:38 ` Andrew Morton
2002-07-02  4:15   ` Bongani [this message]
2002-07-02 11:35     ` Liakakis Kostas
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  0:19 ext3 errors Ferenc Engard
2006-12-09 10:18 Ext3 Errors Jim van Wel
2006-12-09 10:54 ` Jan Kara
2006-12-09 10:57   ` Jim van Wel
2006-12-09 11:34     ` Jan Kara
2006-12-09 11:44       ` Jim van Wel
2006-12-09 11:49         ` Jan Kara
2006-12-09 16:13           ` Jim van Wel
2006-12-11 14:55           ` Jim van Wel
2006-12-17 15:23           ` Jim van Wel

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=1025583346.3267.7.camel@localhost.localdomain \
    --to=bonganilinux@mweb.co.za \
    --cc=akpm@zip.com.au \
    --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