From: "Leandro Guimarães Faria Corcete Dutra" <leandro@dutra.fastmail.fm>
To: Jan Dittmer <j.dittmer@portrix.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 on raid5 failure
Date: Thu, 19 Feb 2004 10:50:00 -0300 [thread overview]
Message-ID: <1077198600.11696.19.camel@moacir.wlt.com.br> (raw)
In-Reply-To: <40346EAD.5010403@portrix.net>
Em Qui, 2004-02-19 às 05:07, Jan Dittmer escreveu:
> Leandro Guimarães Faria Corsetti Dutra wrote:
> >>>On Sun, Jan 18, 2004 at 11:27:54AM +0100, Jan Dittmer wrote:
> >>>>EXT3-fs error (device dm-1): ext3_readdir: bad entry in directory
> >>>>#9783034: rec_len % 4 != 0 - offset=0, inode=1846971784,
> >>>>rec_len=33046, name_len=154
> >>>>Aborting journal on device dm-1.
> >>>>ext3_abort called.
> >>>>EXT3-fs abort (device dm-1): ext3_journal_start: Detected aborted
> >>>>journal Remounting filesystem read-only
> >
> > Has this been resolved? I have a machine due to enter production, am
> > considering going back to 2.4 if there is no further information.
>
> I haven't tried it with 2.6 since this incident. But considering that
> the machine in question crashed a couple of times afterwards, it may
> well be, that a hardware fault caused this initially.
I don't believe so, because I have already run both memtest86 (all
tests, a dozen passes) and cpuburn (burnP6, several hours). I am now
trying to figure out how to run fsx-linux, documentation seems scarce.
> But I simply don't
> dare to put 2.6 again on this machine as I've no real backup of most of
> the data, and restoring some 100 gb from cds is really annoying.
That's the position I think I will have to face. A pity, I was already
hooked into 2.6's speed and LVM2.
--
Leandro Guimarães Faria Corcete Dutra
Maringá, PR, BRASIL +55 (11) 5685 2219
http://br.geocities.com./lgcdutra/ +55 (44) 3028 7467
Soli Deo Gloria! +55 (44) 3028 8335
next prev parent reply other threads:[~2004-02-19 13:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 10:27 Jan Dittmer
2004-01-18 18:02 ` Mike Fedyk
2004-01-19 15:30 ` Theodore Ts'o
2004-01-23 8:22 ` Jan Dittmer
2004-01-27 19:08 ` Theodore Ts'o
2004-01-28 10:54 ` Jan Dittmer
2004-01-29 11:44 ` Theodore Ts'o
2004-02-04 9:24 ` Bas Mevissen
2004-02-04 9:43 ` Nigel Cunningham
2004-02-04 11:38 ` Bas Mevissen
2004-02-04 20:49 ` Nigel Cunningham
2004-02-17 23:14 ` Pavel Machek
2004-02-17 23:58 ` Kiko Piris
2004-02-06 19:18 ` Theodore Ts'o
2004-02-09 8:55 ` Bas Mevissen
2004-02-18 3:07 ` Bill Davidsen
2004-02-19 9:27 ` Bas Mevissen
2004-02-19 19:47 ` Bill Davidsen
2004-01-28 11:06 ` Jan Dittmer
2004-02-19 2:32 ` Leandro Guimarães Faria Corsetti Dutra
2004-02-19 8:07 ` Jan Dittmer
2004-02-19 13:50 ` Leandro Guimarães Faria Corcete Dutra [this message]
2004-02-19 14:58 ` Leandro Guimarães Faria Corsetti Dutra
2004-02-25 17:45 Muhammad L.
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=1077198600.11696.19.camel@moacir.wlt.com.br \
--to=leandro@dutra.fastmail.fm \
--cc=j.dittmer@portrix.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®