From: "J. Ryan Earl" <heretic@clanhk.org>
To: Daniel Brahneborg <basic@wtnord.net>
Cc: Daniel Brahneborg <daniel.com@wtnord.net>, linux-ide@vger.kernel.org
Subject: Re: siimage and two nics
Date: Fri, 26 Dec 2003 05:42:20 +0000 [thread overview]
Message-ID: <3FEBCA3C.5000803@clanhk.org> (raw)
In-Reply-To: <20031226232826.A7057@nettis.grimsta>
Daniel Brahneborg wrote:
>I guess I could, I just needed something to install to.
>It's a file server, so it's the SATA disks that will take
>the biggest hit.
>
>
You should put your busiest disks on the southbridge (via_sata).
>I wouldn't mind using something else, but then I must first
>understand how to get it to stop messing with my PATA hda.
>Would that driver make the SATA disk suddenly appear as IDE
>disks instead of SCSI?
>
>
I don't understand why that matters.
>Checking... oh, it's 1.06 in Linus 2.4.23 kernel. The diff
>doesn't seem to be very much, just a check for 3114 and a fix
>for Seagate drives.
>
>
Have you considered 2.6? It's looking pretty stable with great hardware
support. I'm putting 2.6.0-mm1 on a production server using a RAID1
setup over the SI3112. There's also this patch:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0/2.6.0-mm1/broken-out/ide-siimage-stack-fix.patch
which I have found to be vital for stable operation. If you read back
on the archives I included a diff for 2.4.23_pre8
> scsi3 : sata_via
>
> Vendor: ATA Model: SAMSUNG SP1614C Rev: 0.81
> Type: Direct-Access ANSI SCSI revision: 05
> Vendor: ATA Model: SAMSUNG SP1614C Rev: 0.81
> Type: Direct-Access ANSI SCSI revision: 05
>Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
>Attached scsi disk sdc at scsi2, channel 0, id 0, lun 0
>Attached scsi disk sdd at scsi3, channel 0, id 0, lun 0
>SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> sda: sda1 sda2
>SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
> sdb: sdb1 sdb2
>SCSI device sdc: 312581808 512-byte hdwr sectors (160042 MB)
> sdc: sdc1 sdc2
>SCSI device sdd: 312581808 512-byte hdwr sectors (160042 MB)
> sdd: sdd1 sdd2
>
>
OK. So you have a 4 160GB SATA drives that show up as sda-sdd using
libata. That's cool. I had problems with the sata_sil driver though,
it wasn't stable for me. I'd suggest using the IDE driver until it's
been worked on more. It's alpha right now, but the IDE driver is
production ready by my testing anyway. You just have to modify your
raidtab to account for the new device location (hda/hdc or hde/hdg) of
using the IDE driver.
-ryan
next prev parent reply other threads:[~2003-12-26 23:47 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 [this message]
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
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=3FEBCA3C.5000803@clanhk.org \
--to=heretic@clanhk.org \
--cc=basic@wtnord.net \
--cc=daniel.com@wtnord.net \
--cc=linux-ide@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 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.