Date: Tue, 27 Mar 2007 16:00:15 +0200 From: Marc Santhoff <M.Santhoff@t-online.de> To: Stephen.Clark@seclark.us Cc: freebsd-stable@freebsd.org Subject: Re: pitiful performance of an SATA150 drive Message-ID: <1175004015.336.33.camel@localhost.das.netz> In-Reply-To: <460914EB.4010804@seclark.us> References: <200603010505.k2155HfQ003205@aldan.algebra.com> <44054C5E.5070902@deepcore.dk> <200603011107.09942@aldan> <200703261436.28659@aldan> <1174980137.336.5.camel@localhost.das.netz> <460914EB.4010804@seclark.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Am Dienstag, den 27.03.2007, 08:58 -0400 schrieb Stephen Clark: > Marc Santhoff wrote: > > >Am Montag, den 26.03.2007, 14:36 -0400 schrieb Mikhail Teterin: > > > > > >>Over a year later this remains a problem -- exactly as described below... > >> > >>No other SATA devices are present -- the only other IDE device is the DVD > >>drive. My main disks are SCSI. > >> > >>What's MUCH worse is that the (slowly) written data is also often corrupted... > >>I use the drive to store our vast collection of photos and the backups. Every > >>once in a while I encounter a corrupt JPEG file, and the backups are _always_ > >>corrupt somewhere. Doing something like: > >> > >> dump 0auChf 16 0 - /home | bzip2 -9 > /store/home.0.bz2 > >> > >>always produces a corrupt file (as per ``bzip2 -t''). I used to blame the > >>drive's temperature, but it now sits in its own enclosure and stays under 40 > >>Celsius. > >> > >>When the drive is accessed, there are (according to `systat -vm') many > >>thousands of interrupts 17 -- on my system these are shared between pcm0 and > >>ehci0. Why are these triggered by accessing SATA is unclear, but the Intr's > >>share of the CPU time is often above 80% of one processor's total (I have 4 > >>processors). > >> > >>As I mentioned a year ago, Knoppix was accessing the same drive at much higher > >>speeds, so I don't believe, the problem is with the hardware... > >> > >>Please, advise. Thanks! > >> > >> > > > >FWIW: You could try cleaning the connectors and use a fresh new cable > >for the connection (the spec has a very small value for plugging the > >connectors at the cable). > > > > > Are you referring to how many time the cable can be plugged in and > removed? If so Yes, sorry for my lousy english ... > what is the number? I don't remember the exakt count but it has only two digits. Expect 15 or 50 or so. But IIRC this was SATA 1 and may have changed with SATA 2 having a locking clip at the plug. Marc
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1175004015.336.33.camel>