All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Georgalis <george@galis.org>
To: Sebastian Slota <SSlota@gmx.net>,
	Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: SATA_SIL works with 2.6.7-bk8 seagate drive, but oops
Date: Wed, 30 Jun 2004 00:43:52 -0400	[thread overview]
Message-ID: <20040630044352.GB8841@trot.local> (raw)
In-Reply-To: <29181.1088498805@www29.gmx.net>

On Tue, Jun 29, 2004 at 10:46:45AM +0200, Sebastian Slota wrote:
>Tried Kernel with bk8:
> 
>root@t-rex root # cat /proc/mdstat
>Personalities : [raid0] [raid5] [multipath]
>md1 : active raid5 sdc3[2] sdb3[1] sda3[0]
>261730816 blocks level 5, 128k chunk, algorithm 2 [3/3] [UUU]
>
>md0 : active raid0 sdc2[2] sdb2[1] sda2[0]
>73256064 blocks 128k chunks
>
>unused devices: <none>
>
>root@t-rex root # hdparm -tT /dev/md0
>
>/dev/md0:
>Timing buffer-cache reads: 3896 MB in 2.01 seconds = 1935.71 MB/sec
>Timing buffered disk reads: 274 MB in 3.02 seconds = 90.68 MB/sec
>root@t-rex root # hdparm -tT /dev/md1
>
>/dev/md1:
>Timing buffer-cache reads: 3760 MB in 2.00 seconds = 1879.35 MB/sec
>Timing buffered disk reads: 206 MB in 3.01 seconds = 68.49 MB/secc 
>
>Copy a DVD to HD, both went OK!
>copy data from an ATA HD ( hda ) broke.
>
>I read from ppl they're running linux on some older hardware, maybe thats
>why it doesnt work... but ~25mb/s is nothing for me...
>Also I hear about some patches to limit the speed to ~30MB/s.


I was able to dd ~140 GB with SATA_SIL today, on a stock bk kernel, till
I ran out of disk, no errors. which was a pleasant unexpected surprise.

but when I checked "Timing buffered disk reads" it was around 25 MB/sec
not the ~52 MB/sec I saw before with the oops. The odd thing was this
disk was not in the blacklist so I don't know why it was running slower.

// George


-- 
George Georgalis, Architect and administrator, Linux services. IXOYE
http://galis.org/george/  cell:646-331-2027  mailto:george@galis.org
Key fingerprint = 5415 2738 61CF 6AE1 E9A7  9EF0 0186 503B 9831 1631


  reply	other threads:[~2004-06-30  4:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 17:05 SIIMAGE sata fails with 2.6.7 George Georgalis
2004-06-22 20:25 ` Jeff Garzik
2004-06-23 14:16   ` George Georgalis
2004-06-23 15:32     ` Hugo Mills
2004-06-23 16:35       ` George Georgalis
2004-06-23 17:30         ` Ricky Beam
2004-06-23 20:25           ` George Georgalis
2004-06-23 21:23             ` Fabian Fenaut
2004-06-23 21:50               ` SIIMAGE and sata_sil with 2.6.7-bk George Georgalis
2004-06-24  0:59             ` SIIMAGE sata fails with 2.6.7 Ricky Beam
2004-06-24 15:59               ` SATA_SIL fails with 2.6.7-bk6 seagate drive George Georgalis
2004-06-24 18:46                 ` Ricky Beam
2004-06-25 21:34                   ` SATA_SIL works with 2.6.7-bk8 seagate drive, but oops George Georgalis
2004-06-25 23:16                     ` Linus Torvalds
2004-06-28  2:12                       ` George Georgalis
2004-06-29  8:28                         ` radix-tree.c or sata_sil.c 2.6.7-bk oops George Georgalis
2004-07-02 22:17                           ` George Georgalis
2004-06-29  8:46                     ` SATA_SIL works with 2.6.7-bk8 seagate drive, but oops Sebastian Slota
2004-06-30  4:43                       ` George Georgalis [this message]
2004-06-30  6:16                         ` Jeff Garzik
2004-07-02 23:01                           ` George Georgalis
2004-06-23 14:16   ` SIIMAGE sata fails with 2.6.7 George Georgalis
  -- strict thread matches above, loose matches on Subject: below --
2004-06-26 12:37 SATA_SIL works with 2.6.7-bk8 seagate drive, but oops Albert Cahalan
2004-06-26 15:12 ` Arjan van de Ven
2004-06-26 16:00   ` Linus Torvalds
2004-06-26 16:14     ` Arjan van de Ven
2004-06-26 17:17     ` Albert Cahalan
2004-06-26 17:13   ` Albert Cahalan
2004-06-26 15:54 ` Linus Torvalds

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=20040630044352.GB8841@trot.local \
    --to=george@galis.org \
    --cc=SSlota@gmx.net \
    --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 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.