From: Stefan Traby <stefan@hello-penguin.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Larry McVoy <lm@bitmover.com>,
linux-kernel@vger.kernel.org, tytso@thunk.org
Subject: Re: 2.4.5 data corruption
Date: Tue, 19 Jun 2001 05:00:37 +0200 [thread overview]
Message-ID: <20010619050037.B2512@stefan.sime.com> (raw)
In-Reply-To: <200106122017.f5CKHnf24565@work.bitmover.com> <E15Abiw-00056O-00@the-village.bc.nu>
In-Reply-To: <E15Abiw-00056O-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Jun 14, 2001 at 07:20:06PM +0100
On Thu, Jun 14, 2001 at 07:20:06PM +0100, Alan Cox wrote:
> > Folks, I believe I have a reproducible test case which corrupts data in
> > 2.4.5.
>
> 2.4.5 has an out of date 3ware driver that is short
> + 1.02.00.007 - Fix possible null pointer dereferences in tw_ioctl().
> + Remove check for invalid done function pointer from
> + tw_scsi_queue().
hehe, this one keeps the 3dmd from running here at all.
> That might be a first thing to check
Well, I do not understand how the driver is distributed.
The actual 3ware stuff won't compile on 2.4.x, and the stuff in kernel
is always different from 3ware releases.
I use two 8-port cards (8 disks each) and I see different but
fatal problems on both systems.
Is anyone here using an actual firmware and raid-5 ?
Does it work up to some level on 6800 ?
Anyway, a useful proc-interface would be really cool
(like DAC); I guess that many people would love to get rid
of the - sorry - fucking closed sourced and totally broken 3dmd
which makes an extremly nice product totally useless (you can't
trust it; not only because it's closed source, it simply doesn't
work (except that it wastes memory, that works fine. tested.))
--
ciao -
Stefan
" destroy-your-data-by-3dmd-no-need-for-hammer-anymore CNAME www.3ware.com. "
next prev parent reply other threads:[~2001-06-19 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 20:17 2.4.5 data corruption Larry McVoy
2001-06-13 15:09 ` Nathan Straz
2001-06-13 23:39 ` Chris Mason
2001-06-14 18:20 ` Alan Cox
2001-06-14 22:27 ` Eugene Crosser
2001-06-14 22:49 ` Alan Cox
2001-06-15 19:54 ` Eugene Crosser
2001-06-15 20:17 ` Larry McVoy
2001-06-15 12:02 ` Russell Leighton
2001-06-19 3:00 ` Stefan Traby [this message]
2001-06-19 7:49 ` Alan Cox
2001-06-19 9:13 ` Pedro M. Rodrigues
[not found] <53B208BD9A7FD311881A009027B6BBFB9EACFE@siamese>
2001-06-19 19:01 ` Alan Cox
2001-06-19 20:06 ` Stefan Traby
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=20010619050037.B2512@stefan.sime.com \
--to=stefan@hello-penguin.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=tytso@thunk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).