Bug 100887 - copying from usb 2.0 external drive is very slow
Summary: copying from usb 2.0 external drive is very slow
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pete Zaitcev
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-26 17:30 UTC by Chris Runge
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-10-05 23:18:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Output of /proc/bus/usb/devices (3.38 KB, text/plain)
2003-07-26 17:31 UTC, Chris Runge
no flags Details

Description Chris Runge 2003-07-26 17:30:12 UTC
Description of problem:

I have an IBM ThinkPad T30 running Taroon Beta 1 (WS). The laptop has both USB
2.0 and IEEE1394 Cardbus cards inserted. A SmartDisk FireLite USB 2.0 drive is
connected to the USB 2.0 card.

File maneuvers (copies, moves, etc) on the FireLite are extremely slow,
approaching USB 1.x levels.

All indications, other than speed, are that the drive is in USB 2.0 mode. The
drive lite is blue (rather than green), indicating this mode. In addition, the
output of /proc/bus/usb/devices shows the drive running at USB 2.0 levels 

This problem is not present in Red Hat Linux 9--file transfers are are USB 2.0
speeds.

Version-Release number of selected component (if applicable):

kernel-2.4.21-1.1931.2.349.2.2.ent

Comment 1 Chris Runge 2003-07-26 17:31:25 UTC
Created attachment 93162 [details]
Output of /proc/bus/usb/devices

Comment 2 Chris Runge 2003-07-27 13:50:10 UTC
hmm, I can't seem to reproduce this for the moment. I fsck'd the external disk
(filesystem on it is ext3) and rebooted, and now everything is working as it
should. I also installed the kernel-unsupported package, but I'm not sure if
this latter step would have changed anything or not, since all of the
appropriate drivers appeared to have been loaded before.

Comment 3 Pete Zaitcev 2004-08-19 23:28:09 UTC
Chris, can I close this?


Comment 4 Ernie Petrides 2005-10-05 23:18:20 UTC
Closing due to lack of response.


Note You need to log in before you can comment on or make changes to this bug.