public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Martin Bahlinger <ry42@rz.uni-karlsruhe.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: Fri, 1 Feb 2002 08:55:45 +0300	[thread overview]
Message-ID: <20020201085545.A1034@namesys.com> (raw)
In-Reply-To: <1012499057.704.0.camel@hek411> <Pine.LNX.4.31.0201312133490.652-100000@hek411.hek.uni-karlsruhe.de>
In-Reply-To: <Pine.LNX.4.31.0201312133490.652-100000@hek411.hek.uni-karlsruhe.de>

Hello!

On Thu, Jan 31, 2002 at 09:44:32PM +0100, Martin Bahlinger wrote:
> On 31 Jan 2002, Martin Bahlinger wrote:
> > After applying those patches to 2.5.3 I still got an Oops after a
> > PAP-14030 message. I will try to catch the Oops (have never done this
> > before, may take some time) and feed it to ksymoops.
> I actually had PAP-5760. And after applying the patches it was the
> PAP-14030. During all the tests today my reiserfs got currupted. A

You are the only who reporting these errors for now.
Can you reboot into vanilla 2.5.3 and capture PAP-5760 oops
and all reiserfs-specific output around it? Thank you.

> reiserfsck ran into a segfault when checking the semantic tree. And this

This means you need updated reiserfsprogs.

Bye,
    Oleg

  reply	other threads:[~2002-02-01  5:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 17:44 Current Reiserfs Update / 2.5.2-dj7 Oops Martin Bahlinger
2002-01-31 20:44 ` Martin Bahlinger
2002-02-01  5:55   ` Oleg Drokin [this message]
2002-02-01 22:17     ` Martin Bahlinger
2002-02-02  8:30       ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 10:10 Martin Bahlinger
2002-01-31 13:03 ` Oleg Drokin
2002-01-31 17:20   ` Martin Bahlinger
2002-01-30 14:14 Sebastian Dröge
2002-01-30 14:37 ` Oleg Drokin
2002-01-30 15:39   ` Sebastian Dröge
2002-01-30 16:09     ` Oleg Drokin
2002-01-30 16:40       ` Dave Jones
2002-01-30 16:44         ` Oleg Drokin
2002-01-30 16:55           ` Dave Jones
2002-01-30 17:07             ` Oleg Drokin
2002-01-30 19:10         ` Sebastian Dröge
2002-01-30 19:17           ` Dave Jones
2002-01-31  6:09             ` Oleg Drokin
2002-01-31  9:24             ` Oleg Drokin
2002-01-31 12:49               ` Dave Jones
2002-01-31 12:53                 ` Oleg Drokin
2002-01-31 13:11                   ` Dave Jones
2002-01-31 16:44                     ` Oleg Drokin
2002-01-31 17:23                       ` Sebastian Dröge
2002-01-31 17:45                       ` Chris Mason

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=20020201085545.A1034@namesys.com \
    --to=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ry42@rz.uni-karlsruhe.de \
    /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