From: Oleg Drokin <green@linuxhacker.ru>
To: linux-kernel@vger.kernel.org, ry42@rz.uni-karlsruhe.de
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: Sat, 2 Feb 2002 11:30:52 +0300 [thread overview]
Message-ID: <200202020830.g128UqJ05226@linuxhacker.ru> (raw)
In-Reply-To: <1012499057.704.0.camel@hek411> <Pine.LNX.4.31.0201312133490.652-100000@hek411.hek.uni-karlsruhe.de> <20020201085545.A1034@namesys.com> <1012601878.644.0.camel@hek411>
Martin Bahlinger <ry42@rz.uni-karlsruhe.de> wrote:
MB> Because I don't have my first build of 2.5.3 any more, I had to compile
MB> a new one without any patches applied to it. But now I get a completely
MB> different behaviour: I can boot without problems and get those PAP-5580
MB> oops after a few minutes uptime. I attached the oops message and the
MB> output of ksymoops at the end of this mail.
Ok, thank you. Though this one is already fixed.
MB> I think, the other oops (PAP-14030) happened because of those filesystem
MB> corruptions I mentioned before. Maybe the fs corrupted during the first
Sad, you cannot reproduce it anymore.
>> > reiserfsck ran into a segfault when checking the semantic tree. And this
>> This means you need updated reiserfsprogs.
MB> I use reiserfsprogs 3.x.0j as recommended by linux/Documentation/Changes
We will eventually change that to something more recent.
Bye,
Oleg
next prev parent reply other threads:[~2002-02-02 8:30 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
2002-02-01 22:17 ` Martin Bahlinger
2002-02-02 8:30 ` Oleg Drokin [this message]
-- 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=200202020830.g128UqJ05226@linuxhacker.ru \
--to=green@linuxhacker.ru \
--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