From: Daniel Brahneborg <daniel.com@wtnord.net>
To: "J. Ryan Earl" <heretic@clanhk.org>
Cc: Daniel Brahneborg <daniel.com@wtnord.net>,
linux-ide@vger.kernel.org, linux-raid@vger.kernel.org
Subject: Re: siimage and two nics
Date: Sun, 28 Dec 2003 15:49:33 +0100 [thread overview]
Message-ID: <20031228154933.A5275@nettis.grimsta> (raw)
In-Reply-To: <3FECD15B.1010004@clanhk.org>; from heretic@clanhk.org on Sat, Dec 27, 2003 at 12:24:59AM +0000
On Sat, Dec 27, 2003 at 12:24:59AM +0000, J. Ryan Earl wrote:
> I suggest the -mm tree, it includes all the patches for the siimage
> driver, plus many more. It has been stable in my testing.
I just tried that, but with the same data corruption problem
as with Linus tree: Writing large files on a raid5 disk causes
random data corruption.
I seem to get less DMA problems now though, which is very nice.
/Basic
prev parent reply other threads:[~2003-12-28 14:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 7:54 siimage and drive order problem Daniel Brahneborg
2003-12-26 13:14 ` Ryan Earl
2003-12-26 18:57 ` siimage and two nics (was: drive order problem) Daniel Brahneborg
2003-12-26 3:48 ` siimage and two nics J. Ryan Earl
2003-12-26 22:28 ` Daniel Brahneborg
2003-12-26 5:42 ` J. Ryan Earl
2003-12-27 7:30 ` Daniel Brahneborg
2003-12-27 0:24 ` J. Ryan Earl
2003-12-27 22:40 ` Daniel Brahneborg
2003-12-28 14:49 ` Daniel Brahneborg [this message]
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=20031228154933.A5275@nettis.grimsta \
--to=daniel.com@wtnord.net \
--cc=heretic@clanhk.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.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