From: maney@two14.net (Martin Maney)
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Martin Maney <maney@two14.net>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: 2.4.22-rc2 ext2 filesystem corruption
Date: Sat, 3 Jan 2004 19:12:22 -0600 [thread overview]
Message-ID: <20040104011222.GA1433@furrr.two14.net> (raw)
In-Reply-To: <200310311941.31930.bzolnier@elka.pw.edu.pl>
On Fri, Oct 31, 2003 at 07:52:21PM +0100, Bartlomiej Zolnierkiewicz wrote:
>
> [ http://www.ussg.iu.edu/hypermail/linux/kernel/0308.1/1164.html
> for people seeing this subject for the first time ]
Sorry the reply is so belated, but by the time this patch came along I
was feeling like I had been more than a little foolish to test this on
a live (and very necessary) system as I had been doing. I've finally
gotten hardware rearranged so that I can feel safe about this.
> Can you try booting with "hdX=autotune" (hdX==your drive) kernel parameter?
> The next thing to try is the attached patch (against 2.4.23-pre9), which
> sanitizes 66MHz clock usage -> now 66MHz clock is "enabled" before starting
Okay, by now I have 2.4.23 installed, and with that version (and booting
from a drive not connected to the Promise controller, a mirror pair on
a 3ware controller, in fact) I no longer seem to be able to recreate
the corruption that was previously so repeatable. The autotune
parameter makes no difference: it just works.
If this issue is still of interest (ie, it's just by luck that .23
works), I can do further testing for a while, but the drive that's on
the Promise will be getting repurposed sooner or later.
--
Faced with the choice between changing one's mind and proving there is
no need to do so, almost everyone gets busy on the proof. -- JKG
next prev parent reply other threads:[~2004-01-04 1:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 18:52 [PATCH] Re: 2.4.22-rc2 ext2 filesystem corruption Bartlomiej Zolnierkiewicz
2003-11-03 0:50 ` Benjamin Herrenschmidt
2004-01-04 1:12 ` Martin Maney [this message]
2004-01-04 2:07 ` Bartlomiej Zolnierkiewicz
2004-01-08 16:25 ` Martin Maney
2004-01-10 23:18 ` Martin Maney
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=20040104011222.GA1433@furrr.two14.net \
--to=maney@two14.net \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maney@pobox.com \
/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.