From: Oleg Drokin <green@namesys.com>
To: Dave Jones <davej@suse.de>,
Sebastian Dr?ge <sebastian.droege@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: Current Reiserfs Update / 2.5.2-dj7 Oops
Date: Wed, 30 Jan 2002 19:44:08 +0300 [thread overview]
Message-ID: <20020130194408.A2153@namesys.com> (raw)
In-Reply-To: <20020130151420.40e81aef.sebastian.droege@gmx.de> <20020130173715.B2179@namesys.com> <20020130163951.13daca94.sebastian.droege@gmx.de> <20020130190905.A820@namesys.com> <20020130174011.L24012@suse.de>
In-Reply-To: <20020130174011.L24012@suse.de>
Hello!
On Wed, Jan 30, 2002 at 05:40:11PM +0100, Dave Jones wrote:
> > I can reproduce this problem on IDE only.
> > Hm, may be this is IDE corruption thing, Andre Hendrick spoke about,
> > or was it fixed already?
> > I am looking into it anyway.
> There were no IDE changes in my tree recently, and its strange
> that this only shows up in reiserfs since the new set of patches
> went in. I've no reports from users of other filesystems with any
> problems, so I'm suspecting a rogue change in your last update.
> Finding a common factor seems tricky, as it works flawlessly here
> on IDE [*], but dies instantly for others.
You do not play with a hdparm in your boot scripts, do you?
I do (will retry without this now).
How about others?
Bye,
Oleg
next prev parent reply other threads:[~2002-01-30 16:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 14:14 Current Reiserfs Update / 2.5.2-dj7 Oops 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 [this message]
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
-- 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-31 17:44 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
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=20020130194408.A2153@namesys.com \
--to=green@namesys.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.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