linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Brahneborg <daniel.com@wtnord.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Daniel Brahneborg <daniel.com@wtnord.net>, linux-raid@vger.kernel.org
Subject: Re: Status of Promise drivers?
Date: Tue, 30 Dec 2003 21:18:26 +0100	[thread overview]
Message-ID: <20031230211826.F14399@nettis.grimsta> (raw)
In-Reply-To: <3FF1D8AE.2000107@pobox.com>; from jgarzik@pobox.com on Tue, Dec 30, 2003 at 02:57:34PM -0500

On Tue, Dec 30, 2003 at 02:57:34PM -0500, Jeff Garzik wrote:
> Daniel Brahneborg wrote:
> > On Tue, Dec 30, 2003 at 02:06:41PM -0500, Jeff Garzik wrote:
> >>Those who ignore the author stating the Silicon Image driver is _alpha_ 
> >>and unfinished do so at their own risk.
> > 
> > Is this true for both the IDE driver and the SCSI driver?
> 
> Only the "scsi" driver, sata_sil.  People do have some problems with the 
> IDE driver siimage, but it is on the whole much more stable.

I'm one of the people with problems...

> > Is the same driver used for the TX4 card? Checking my logs even the
> > VIA driver seems to have problems running under Raid. Both Raid1
> > and Raid5 gives me corrupted files, unless I turn off DMA.
> 
> sata_promise is used for all known Promise SATA cards.

Great!

> Which VIA driver are you referring to?  And PATA or SATA?  You need to 
> be more specific :)   The drivers/ide via82cxxx driver seems to work for 
> PATA.  The sata_via ("scsi") driver and the generic IDE driver work for 
> VIA SATA, but people have reported problems on x86-64.

SATA, with the via82cxxx driver.  It works fine for simple partitions,
which I guess is what most people uses.

In short: First I went 100% scsi (except for / on hda) with sata_sil
and sata_via. This made my computer halt when I activated my second
network card (8139 + via-rhine or another 8139). Then I went 100% ide
with the via82cxxx and siimage drivers, which made the network cards
work.  Disks on the VIA interface worked fine for simple file systems
but failed when used for Raid. Disks on the Silicon Image interface
failed both.  It even got badblocks from the Ext2 suite to report tons
of failures.  Smartmontools has no complaints, so the disks as such
are ok.

/Basic


  reply	other threads:[~2003-12-30 20:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 19:00 Status of Promise drivers? Daniel Brahneborg
2003-12-30 19:06 ` Jeff Garzik
2003-12-30 19:24   ` Daniel Brahneborg
2003-12-30 19:57     ` Jeff Garzik
2003-12-30 20:18       ` Daniel Brahneborg [this message]
2003-12-30 20:25         ` Jeff Garzik
2003-12-30 20:38           ` Daniel Brahneborg
2003-12-30 23:38             ` Jeff Garzik
2004-01-10 15:14           ` Daniel Brahneborg
2003-12-30 20:21       ` Hendrik Visage
2003-12-30 20:27         ` Jeff Garzik
2004-02-03 18:23   ` Daniel Brahneborg
2004-02-04 15:02     ` Gunnlaugur Thor Briem
2004-02-06 21:13       ` Gunnlaugur Thor Briem
2003-12-30 23:21 ` Status of HighPoint / " Daniel Brahneborg
2003-12-30 23:37   ` Jeff Garzik
2003-12-30 23:55     ` jlewis

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=20031230211826.F14399@nettis.grimsta \
    --to=daniel.com@wtnord.net \
    --cc=jgarzik@pobox.com \
    --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;
as well as URLs for NNTP newsgroup(s).