From: Ville Herva <v@iki.fi>
To: Willy Tarreau <w@1wt.eu>
Cc: Jan Kara <jack@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.35 SMP: ext3_readdir: bad entry in directory #323888: rec_len is smaller than minimal
Date: Thu, 20 Sep 2007 16:25:33 +0300 [thread overview]
Message-ID: <20070920132533.GC5076@vianova.fi> (raw)
In-Reply-To: <20070920132055.GB12291@1wt.eu>
On Thu, Sep 20, 2007 at 03:20:55PM +0200, you [Willy Tarreau] wrote:
> OK. And your config seems perfectly standard.
>
> > gcc 2.96-129:
> > cat /proc/version
> > Linux version 2.4.35 (root) (gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2)) #1 SMP Thu Aug 9 10:35:37 EEST 2007
>
> I used not to trust 2.96, but I wouldn't accuse it now.
The box was virtualized a while ago and 2.4.32-rc1 and earlier 2.4 compiled
with the same compiler ran very solidly for years. It was UP before
virtualization, though.
> > share of chipset bugs with older Via chipsets, but I think it's very likely
> > in this case.
>
> I think you meant "unlikely".
Yep, sorry for the typo.
> > This could very well be a VMware bug, but I wanted to know if this rings
> > bells for someone.
>
> It could also be a problem with the host OS, drivers, hardware, etc...
Yes, pretty much anything. There's no solid evidency of anything, only
guesses of what might be more likely and what might be less likely...
If it happens again, I'll try to debug more.
-- v --
v@iki.fi
prev parent reply other threads:[~2007-09-20 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 12:23 2.4.35 SMP: ext3_readdir: bad entry in directory #323888: rec_len is smaller than minimal Ville Herva
2007-09-18 15:12 ` Jan Kara
2007-09-18 16:09 ` Ville Herva
2007-09-18 16:22 ` Jan Kara
2007-09-18 16:33 ` Ville Herva
2007-09-18 21:47 ` Willy Tarreau
2007-09-20 12:45 ` Ville Herva
2007-09-20 13:20 ` Willy Tarreau
2007-09-20 13:25 ` Ville Herva [this message]
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=20070920132533.GC5076@vianova.fi \
--to=v@iki.fi \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=w@1wt.eu \
/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