* slow external firewire drive
@ 2005-10-27 1:56 Eric Edgar
2005-10-27 3:33 ` Matthew Wilcox
2005-10-27 7:48 ` Stefan Richter
0 siblings, 2 replies; 5+ messages in thread
From: Eric Edgar @ 2005-10-27 1:56 UTC (permalink / raw)
To: linux-scsi
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
Hi,
I am having trouble with an external firewire drive. I have a texas
instruments based card and a maxtor external enclosure. Whenever I
try to do anything with this disk the iowait goes through the roof and
it can take half an hour or more to untar an 80mb file. I am not sure
if its something with my computer or the card or the enclosure. Any
help would be greatly appreciated.
hci1394: $Rev: 1313 $ Ben Collins <bcollins@debian.org>
PCI: Enabling device 0000:00:0c.0 (0014 -> 0016)
PCI: Found IRQ 11 for device 0000:00:0c.0
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11] MMIO=[d9800000-d98007ff] Max
Packet=[2048]
sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
ieee1394: sbp2: Try serialize_io=0 for better performance
ieee1394: sbp2: Logged into SBP-2 device
ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Vendor: Maxtor Model: 1394 storage Rev: v1.3
Type: Direct-Access-RBC ANSI SCSI revision: 04
SCSI device sda: 156355584 512-byte hdwr sectors (80054 MB)
sda: asking for cache data failed
sda: assuming drive cache: write through
SCSI device sda: 156355584 512-byte hdwr sectors (80054 MB)
sda: asking for cache data failed
sda: assuming drive cache: write through
sda: sda1
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 14
hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 644 MB in 2.01 seconds = 320.40 MB/sec
Timing buffered disk reads: 8 MB in 3.09 seconds = 2.59 MB/sec
uname -a
2.6.14-rc4
I dont seem to see any error messages ... just bad performance.
Thanks in advance,
Eric
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: slow external firewire drive
2005-10-27 1:56 slow external firewire drive Eric Edgar
@ 2005-10-27 3:33 ` Matthew Wilcox
2005-10-27 7:48 ` Stefan Richter
1 sibling, 0 replies; 5+ messages in thread
From: Matthew Wilcox @ 2005-10-27 3:33 UTC (permalink / raw)
To: Eric Edgar; +Cc: linux-scsi
On Thu, Oct 27, 2005 at 01:56:55AM +0000, Eric Edgar wrote:
> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
> ieee1394: sbp2: Try serialize_io=0 for better performance
... did you try that?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: slow external firewire drive
2005-10-27 1:56 slow external firewire drive Eric Edgar
2005-10-27 3:33 ` Matthew Wilcox
@ 2005-10-27 7:48 ` Stefan Richter
2005-10-27 14:42 ` James Bottomley
[not found] ` <20051027124154.GD14010@toucan.gentoo.org>
1 sibling, 2 replies; 5+ messages in thread
From: Stefan Richter @ 2005-10-27 7:48 UTC (permalink / raw)
To: linux-scsi; +Cc: Eric Edgar, Matthew Wilcox
Eric Edgar wrote:
> I am having trouble with an external firewire drive. I have a texas
> instruments based card and a maxtor external enclosure. Whenever I
> try to do anything with this disk the iowait goes through the roof and
> it can take half an hour or more to untar an 80mb file. I am not sure
> if its something with my computer or the card or the enclosure. Any
> help would be greatly appreciated.
>
>
> hci1394: $Rev: 1313 $ Ben Collins <bcollins@debian.org>
> PCI: Enabling device 0000:00:0c.0 (0014 -> 0016)
> PCI: Found IRQ 11 for device 0000:00:0c.0
> ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[11] MMIO=[d9800000-d98007ff] Max
> Packet=[2048]
> sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
> ieee1394: sbp2: Try serialize_io=0 for better performance
Like Matthew already mentioned, a "modprobe sbp2 serialize_io=0" before
sbp2 is automatically loaded, or the line "options sbp2 serialize_io=0"
in /etc/modprobe.conf may achieve better performance. However as far as
I know, the performance gain is below variance of measurement with
typical 1394a ("FireWire 400") disks. Only 1394b/S800 ("FireWire 800")
disks show a noticable improved throughput with that option. But it is
not an improvement by an order of magnitude. It may be something like
30% better throughput with S800 devices.
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> Vendor: Maxtor Model: 1394 storage Rev: v1.3
> Type: Direct-Access-RBC ANSI SCSI revision: 04
> SCSI device sda: 156355584 512-byte hdwr sectors (80054 MB)
> sda: asking for cache data failed
> sda: assuming drive cache: write through
> SCSI device sda: 156355584 512-byte hdwr sectors (80054 MB)
> sda: asking for cache data failed
> sda: assuming drive cache: write through
> sda: sda1
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
> Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 14
>
>
> hdparm -tT /dev/sda
>
> /dev/sda:
> Timing cached reads: 644 MB in 2.01 seconds = 320.40 MB/sec
> Timing buffered disk reads: 8 MB in 3.09 seconds = 2.59 MB/sec
This is really bad. 3.5" S400 disks on S400 host adapters show typically
about 23 MB/s with hdparm, 2.5" disks also nearly as much.
At least we can rule out a filesystem related problem with that info.
> uname -a
> 2.6.14-rc4
>
> I dont seem to see any error messages ... just bad performance.
I did not hear of a serious performance regression with that kernel yet.
I tested 2.6.14-rc3 and -rc5 myself but they should behave like -rc4.
Anyhow, if there are no error messages, one possible cause are
recoverable transport errors at the FireWire bus. Perhaps a syslog with
ieee1394 compiled with the "excessive debug output" option could provide
clues. Note however that (a) such logs may become really huge, (b) the
logging activity might actually mask some problems of the Heisenbug kind
out, (c) these logs are no pleasure to read and I for one am typically
slow to read and respond to such reports...
BTW, I have a no-name 1394b FireWire 800 card with TI chipset whith an
obviously buggy PHY chip which causes extreme slow transfers, even
slower than what you see. I need to force this card into 1394a
arbitration mode and to optimize the gap count in order to bring that
card up to speed. Both is not implemented directly in the 1394 drivers yet.
What is the manufacturer and model of the card and which link chip and
PHY chip is it built on? (The PHY chip can only be found out by looking
on the card, not by lspci and the like. lspci shows only the link chip.)
--
Stefan Richter
-=====-=-=-= =-=- ==-==
http://arcgraph.de/sr/
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: slow external firewire drive
2005-10-27 7:48 ` Stefan Richter
@ 2005-10-27 14:42 ` James Bottomley
[not found] ` <20051027124154.GD14010@toucan.gentoo.org>
1 sibling, 0 replies; 5+ messages in thread
From: James Bottomley @ 2005-10-27 14:42 UTC (permalink / raw)
To: Stefan Richter; +Cc: linux-scsi, Eric Edgar, Matthew Wilcox
On Thu, 2005-10-27 at 09:48 +0200, Stefan Richter wrote:
> I did not hear of a serious performance regression with that kernel yet.
> I tested 2.6.14-rc3 and -rc5 myself but they should behave like -rc4.
Yes, for unrelated reasons, I've done u320 testing with -rc5. I can
actually get it up to 320MB/s if I read and write entirely from the disk
cache, so I think our current throughput is OK in the generic systems.
James
^ permalink raw reply [flat|nested] 5+ messages in thread[parent not found: <20051027124154.GD14010@toucan.gentoo.org>]
* Re: slow external firewire drive
[not found] ` <20051027124154.GD14010@toucan.gentoo.org>
@ 2005-10-30 7:47 ` Stefan Richter
0 siblings, 0 replies; 5+ messages in thread
From: Stefan Richter @ 2005-10-30 7:47 UTC (permalink / raw)
To: linux-scsi; +Cc: Eric Edgar
Eric Edgar wrote on 2005-10-27:
> I have tried the different serialize_io option and it didnt help much.
>
> it is a s400 based card.
>
> Here are the numbers off the 2 biggest chips on the card.
>
> belkin f5u503
>
> CHIP 1
> tsb12lv26
> ca-22a752t
> f731652a
>
> CHIP 2
> 22any0ct
> tsb41ab3
...
I have not heard anything negative about Belkin hardware so far. Also,
TI lists only one erratum concerning the TSB41AB3 which is not related
to the low throughput. The culprit is probably either the Maxtor
FireWire enclosure (PHY, link layer controller & IDE bridge, firmware,
or perhaps even the included HDD) or our software...
>>> Vendor: Maxtor Model: 1394 storage Rev: v1.3
>>> Type: Direct-Access-RBC ANSI SCSI revision: 04
>>>SCSI device sda: 156355584 512-byte hdwr sectors (80054 MB)
...
>>>hdparm -tT /dev/sda
>>>
>>>/dev/sda:
>>>Timing cached reads: 644 MB in 2.01 seconds = 320.40 MB/sec
>>>Timing buffered disk reads: 8 MB in 3.09 seconds = 2.59 MB/sec
...
>>>2.6.14-rc4
>>>
>>>I dont seem to see any error messages ... just bad performance.
Maxtor's currently available enclosures are noticeable slower than
comparable products:
http://www.macworld.com/2005/10/reviews/firewiremain/index1.php
Although according to these application test on OS X, they should not be
as extremely slow as hdparm measures.
I remember though that Maxtor FireWire drives have been used under Linux
before. Alas www.linux1394.org and its hardware compatibility list are
offline again at the moment.
That is all I can say about it so far.
--
Stefan Richter
-=====-=-=-= =-=- ====-
http://arcgraph.de/sr/
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-10-30 7:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-27 1:56 slow external firewire drive Eric Edgar
2005-10-27 3:33 ` Matthew Wilcox
2005-10-27 7:48 ` Stefan Richter
2005-10-27 14:42 ` James Bottomley
[not found] ` <20051027124154.GD14010@toucan.gentoo.org>
2005-10-30 7:47 ` Stefan Richter
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox