From: Andreas Dilger <adilger@clusterfs.com>
To: Oliver Feiler <kiza@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ext3 errors with 2.4.18
Date: Tue, 14 May 2002 04:49:22 -0600 [thread overview]
Message-ID: <20020514104922.GR12975@turbolinux.com> (raw)
In-Reply-To: <3CD6AE7A.FBEB5726@delusion.de> <200205141238.11104.kiza@gmx.net>
On May 14, 2002 12:38 +0200, Oliver Feiler wrote:
> On Monday 06 May 2002 18:25, Udo A. Steinberg wrote:
> > Hi,
> >
> > With Linux 2.4.18, I'm getting multiple of the following error:
> >
> > EXT3-fs error (device ide0(3,2)): ext3_readdir: bad entry in directory
> > #1966094: rec_len % 4 != 0 - offset=0, inode=3180611420, rec_len=53134,
> > name_len=138
>
> Hi,
>
> I experienced the same problem with ext3 + 2.4.18 on a RAID-1. Out of nowhere
> the following error popped up in the syslog, no other surrounding error
> messages. The fs was mounted read-only automatically. After reboot and fsck
> there were /a lot/ of errors on the disk. Virtually all errors fsck knows I
> think. :) After fsck ran multiple times on the disk, lost+found was filled
> with stuff from all accross the disk, but other than that the fs seems to
> have survived it.
There have been several reports of strange ext3 errors when running on
MD RAID. I don't know if anyone is looking into this yet.
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
next prev parent reply other threads:[~2002-05-14 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 16:25 Ext3 errors with 2.4.18 Udo A. Steinberg
2002-05-06 17:20 ` Mike Fedyk
2002-05-06 17:32 ` Udo A. Steinberg
2002-05-06 21:11 ` Andrew Morton
2002-05-14 10:38 ` Oliver Feiler
2002-05-14 10:49 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 10:59 Neil Conway
2002-05-14 11:37 ` Oliver Feiler
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=20020514104922.GR12975@turbolinux.com \
--to=adilger@clusterfs.com \
--cc=kiza@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.