public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Alan <alan@clueserver.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rogier Wolff <R.E.Wolff@BitWizard.nl>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Question on siig sata 3 controller
Date: Tue, 10 Aug 2010 15:48:18 +0200	[thread overview]
Message-ID: <20100810134817.GA25874@bitwizard.nl> (raw)
In-Reply-To: <1276622732.6843.2.camel@zowie.clueserver.org>

On Tue, Jun 15, 2010 at 10:25:32AM -0700, Alan wrote:
> On Tue, 2010-06-15 at 16:01 +0100, Alan Cox wrote: 
> > > Is one of these modules the driver for this controller? I think it's
> > > AHCI: lshw says it uses ports cc00 ... and a bunch of others, and
> > > those ports are claimed by ahci according to /proc/ioports. Ah! I need
> > > better eyes. lshw already mentions that it's ahci...
> > 
> > AHCI will be driving it.
> 
> I have seen this problem with the 2.6.33 kernel in Fedora 13. The
> problem goes away in 2.6.35-rc3. (Though networking is fubared for me on
> that kernel, so I have not migrated to it.)
> 
> My understanding is the "fix" in the driver was to blacklist ncq for
> that controller. I have not verified that yet.
 
One of my disks died again a while ago. So I went to the machine to
replace the drive. But I forgot to write down which one had died. So I
started it up again. Now I had 7 disks again like before, but a
different drive was now "gone". So my RAID had only 6 out of 8 drives
and was "gone". Together with some 4.7T worth of data on it.... 

Next I went to the machine with a spare sata card. I removed the
drives from the ASUS U3S6 card, and put them on the old pci sata card. 

By the time I logged in on the machine, the RAID had found 8/8 drives
and I think it had already started rebuilding..... 

I now haven't had any problems with the drives in more than a week.

Performance of the raid has dropped from 600Mb to around 400Mb/sec,
obviously because the PCI card cannot handle 200Mb/sec of disk IO. 

I'm open to suggestions for cheap highperformance WORKING PCIe sata
cards.... 

	Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
**    Delftechpark 26 2628 XH  Delft, The Netherlands. KVK: 27239233    **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

  reply	other threads:[~2010-08-10 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10  4:39 Question on siig sata 3 controller Alan
2010-06-10  8:53 ` Jeff Garzik
2010-06-10 16:28   ` alan
2010-06-11  2:08   ` Alan
2010-06-15  6:57     ` Rogier Wolff
2010-06-15 10:07       ` Alan Cox
2010-06-15 14:53         ` Rogier Wolff
2010-06-15 15:01           ` Alan Cox
2010-06-15 17:25             ` Alan
2010-08-10 13:48               ` Rogier Wolff [this message]
2010-08-12  0:27                 ` alan

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=20100810134817.GA25874@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=alan@clueserver.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@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