linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Daniel Brahneborg <daniel.com@wtnord.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Status of Promise drivers?
Date: Tue, 30 Dec 2003 18:38:58 -0500	[thread overview]
Message-ID: <3FF20C92.9060700@pobox.com> (raw)
In-Reply-To: <20031230213828.G14399@nettis.grimsta>

Daniel Brahneborg wrote:
> On Tue, Dec 30, 2003 at 03:25:15PM -0500, Jeff Garzik wrote:
> 
>>Daniel Brahneborg wrote:
>>
>>>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.
>>
>>I definitely recommend IDE siimage driver for Silicon Image SATA (though 
>>I will announce when my driver is fixed).
> 
> 
> Not even the IDE driver handles raid correctly though, and the
> badblocks thing was with that IDE driver.  Is there any debug information
> I can provide you with, in order to help you fix this?

Not really, I mainly need free time :)


>>For VIA SATA, neither IDE nor libata program the chipset 100%, so I'm 
>>not surprised you're seeing failures.  I'm working with VIA to get more 
>>details as we speak.  They've been helpful so far.  I would recommend 
>>sata_via over the generic IDE driver, but that's sorta a toss-up at present.
> 
> 
> Good, I like companies that are helpful. What would you estimate
> the time frame for working raid support to?  10 minutes? A week?
> A month?  Kernel 2.8?

I would say "under a day"

	Jeff



  reply	other threads:[~2003-12-30 23:38 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
2003-12-30 20:25         ` Jeff Garzik
2003-12-30 20:38           ` Daniel Brahneborg
2003-12-30 23:38             ` Jeff Garzik [this message]
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=3FF20C92.9060700@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=daniel.com@wtnord.net \
    --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).