From: Andrew Morton <akpm@zip.com.au>
To: Oleg Drokin <green@namesys.com>
Cc: Berjoza Roman <b_rom_s@4enet.by>, linux-kernel@vger.kernel.org
Subject: Re: reiserfs+updatedb=oops
Date: Thu, 24 Jan 2002 12:38:34 -0800 [thread overview]
Message-ID: <3C5070CA.40B96B00@zip.com.au> (raw)
In-Reply-To: <20020123161944Z289790-13996+10616@vger.kernel.org> <20020124132944.A20375@namesys.com> <20020124105404.02895225988@angband.namesys.com>, <20020124105404.02895225988@angband.namesys.com> <20020124135722.A26375@namesys.com>
Oleg Drokin wrote:
>
> Hello!
>
> On Thu, Jan 24, 2002 at 12:56:21PM +0200, Berjoza Roman wrote:
>
> > Yes, yes, yes - you right. I have the same oops on ext2 today.
> > Sorry for incorrect report - i am newcomer in kernel testing, and updatedb
> > was not triggered :(
> You mean you are able to reproduce this reliably?
> Can you reproduce on 2.4.18-pre6?
> If yes, I believe VFS folks would be interested.
>
It just looks like a standard memory-corruption crash. We're
seeing these on a daily basis - far too many for it to
be hardware problems. I'm collecting them, trying to
pick a pattern.
Berjoza, please send your .config and a description
of what sorts of things the machine is being used
for (network server, firewall, etc).
Thanks.
prev parent reply other threads:[~2002-01-24 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-23 16:23 reiserfs+updatedb=oops Berjoza Roman
2002-01-24 10:29 ` reiserfs+updatedb=oops Oleg Drokin
[not found] ` <20020124105404.02895225988@angband.namesys.com>
2002-01-24 10:57 ` reiserfs+updatedb=oops Oleg Drokin
2002-01-24 20:38 ` Andrew Morton [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=3C5070CA.40B96B00@zip.com.au \
--to=akpm@zip.com.au \
--cc=b_rom_s@4enet.by \
--cc=green@namesys.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 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.