Alan,
> >
> > !/usr/bin/perl
> > while(1)
> > {
> > print "$i\n";
> > print `date`;
> > print `cp -r /home/test /media/usbdisk/`;
> > print `date`;
> > print `rm -rf /media/usbdisk/test`;
> > }
>
> This is not a good test.
Well, I was not going to run benchmarks. It is just when I tried to edit a
movie that I saved on
the external USB drive the connection got so bad that it was almost impossible
to work. That's
when I started experimenting. Whether it is a good way to measure the USB
transfer rate itself,
does not matter for me too much since this test should work reasonably well, I
would think, if
there are no software or hardware issues.
> Mainly you are measuring the computer's buffer
> capacity, not the transfer speed to the drive.
Which buffer is that? Is it configurable or is it built into hardware?
> > I do not have any trouble using the same drive (Maxtor 300GB, 7200 rpms,
> > installed into MadDog
> > USB2.0 enclosure) with another laptop (also running Fedora Core 4 but 32
> > bit), so it is not
> the
> > drive or the cable problem. Also, I tried another similar drive partitioned
> > half ext3 and half
> > ntfs. Same problem under Linux but the same burn test seems to work fine
> > with windows half of
> the
> > drive. So most likely it is not a hardware problem with my laptop.
>
> Don't be so sure about that. I have a USB drive and cable that don't work
> on one computer. Switching any one of the three (drive, cable, or
> computer) makes things work again.
If it is a hardware problem it must be with the laptop because it behaves the
same way with 2
different external drives and one memory stick that I tried. Also I
successfully use those USB
devices with other computers. However, at first glance I did not observe any
problems under
Windows (although I have spent much less time using USB under windows; what is
a good way to test
USB under Windows? I was using the same perl script under Cygwin) So my main
suspect now is Linux
that does not support my too new and exotic hardware. I am trying to decide
what to do with the
laptop: I have two weeks during which I can return it (which expire in couple
days). If it is a
hardware problem, I would think that the whole motherboard has to be changed. I
do not know for
sure but I would think that on a laptop USB is not a separate card but built
into the motherboard.
Right?
>
> You're probably getting a lot of communication errors. Have you looked
> for error messages in the system log?
>
>
At the beginning, if USB disk manages to connect, it looks good
=======================
Jan 21 17:06:31 orca kernel: usb 1-5: new high speed USB device using ehci_hcd
and address 4
Jan 21 17:06:31 orca kernel: usb 1-5: Product: USB2.0 Storage Device
Jan 21 17:06:31 orca kernel: usb 1-5: Manufacturer: Cypress Semiconductor
Jan 21 17:06:31 orca kernel: usb 1-5: SerialNumber: DEF10A32960E
Jan 21 17:06:32 orca kernel: Initializing USB Mass Storage driver...
Jan 21 17:06:32 orca kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Jan 21 17:06:32 orca kernel: usbcore: registered new driver usb-storage
Jan 21 17:06:32 orca kernel: USB Mass Storage support registered.
Jan 21 17:06:37 orca kernel: Vendor: Maxtor 4 Model: A300J0 Rev:
0000
Jan 21 17:06:37 orca kernel: Type: Direct-Access ANSI
SCSI revision: 00
Jan 21 17:06:37 orca kernel: SCSI device sdb: 585940320 512-byte hdwr sectors
(300001 MB)
Jan 21 17:06:37 orca kernel: sdb: assuming drive cache: write through
Jan 21 17:06:37 orca kernel: SCSI device sdb: 585940320 512-byte hdwr sectors
(300001 MB)
Jan 21 17:06:37 orca kernel: sdb: assuming drive cache: write through
Jan 21 17:06:37 orca kernel: sdb:<7>usb-storage: queuecommand called
Jan 21 17:06:37 orca kernel: sdb1
Jan 21 17:06:37 orca kernel: sd 2:0:0:0: Attached scsi disk sdb
Jan 21 17:06:37 orca scsi.agent[5080]: disk at
/devices/pci0000:00/0000:00:10.4/usb1/1-5/1-5:1.0/host2/target2:0:0/2:0:0:0
Jan 21 17:06:37 orca fstab-sync[5103]: added mount point /media/usbdisk1 for
/dev/sdb1
Jan 21 17:07:46 orca automount[5162]: failed to mount /misc/.directory
Jan 21 17:07:46 orca automount[5163]: >> /usr/sbin/showmount: can't get address
for .directory
Jan 21 17:07:46 orca automount[5163]: lookup(program): lookup for .directory
failed
Jan 21 17:07:46 orca automount[5163]: failed to mount /net/.directory
Jan 21 17:07:52 orca kernel: kjournald starting. Commit interval 5 seconds
Jan 21 17:07:52 orca kernel: EXT3-fs warning: maximal mount count reached,
running e2fsck is
recommended
Jan 21 17:07:52 orca kernel: EXT3 FS on sdb1, internal journal
Jan 21 17:07:52 orca kernel: EXT3-fs: recovery complete.
Jan 21 17:07:52 orca kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 21 17:07:52 orca kernel: SELinux: initialized (dev sdb1, type ext3), uses
xattr
Jan 21 17:09:44 orca su(pam_unix)[5308]: session opened for user root by
(uid=500)
Jan 21 17:09:46 orca kernel: : Bulk Command S 0x43425355 T 0x208c L 122880 F 0
Trg 0 LUN 0 CL 10
=======================
However, an hour later (wow! it is the first time it worked for so long!
usually it is a matter of
minutes before it breaks) things get bad:
=======================
Jan 21 18:08:28 orca kernel: usb 1-5: reset high speed USB device using
ehci_hcd and address 4
Jan 21 18:08:40 orca kernel: usb 1-5: device not accepting address 4, error -110
Jan 21 18:08:40 orca kernel: usb 1-5: reset high speed USB device using
ehci_hcd and address 4
Jan 21 18:08:51 orca kernel: usb 1-5: device not accepting address 4, error -110
Jan 21 18:08:51 orca kernel: usb 1-5: reset high speed USB device using
ehci_hcd and address 4
Jan 21 18:09:02 orca kernel: usb 1-5: device not accepting address 4, error -110
Jan 21 18:09:02 orca kernel: usb 1-5: reset high speed USB device using
ehci_hcd and address 4
Jan 21 18:09:12 orca kernel: usb 1-5: device not accepting address 4, error -110
Jan 21 18:09:12 orca kernel: usb 1-5: USB disconnect, address 4
Jan 21 18:09:12 orca kernel: sd 2:0:0:0: scsi: Device offlined - not ready
after error recovery
Jan 21 18:09:12 orca kernel: sd 2:0:0:0: SCSI error: return code = 0x10000
Jan 21 18:09:13 orca kernel: end_request: I/O error, dev sdb, sector 412157375
Jan 21 18:09:13 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:13 orca kernel: Buffer I/O error on device sdb1, logical block
51718619
Jan 21 18:09:13 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:13 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:13 orca kernel: Buffer I/O error on device sdb1, logical block
51719644
Jan 21 18:09:13 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:13 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:13 orca kernel: Buffer I/O error on device sdb1, logical block
51720669
Jan 21 18:09:13 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:13 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:13 orca kernel: Buffer I/O error on device sdb1, logical block
51721694
Jan 21 18:09:13 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:14 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:17 orca kernel: Buffer I/O error on device sdb1, logical block
51722719
Jan 21 18:09:21 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:24 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:27 orca kernel: Buffer I/O error on device sdb1, logical block
51723744
Jan 21 18:09:29 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:31 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:32 orca kernel: Buffer I/O error on device sdb1, logical block
51724769
Jan 21 18:09:33 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:34 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:35 orca kernel: Buffer I/O error on device sdb1, logical block
51725794
Jan 21 18:09:36 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:36 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:37 orca kernel: Buffer I/O error on device sdb1, logical block
51726819
Jan 21 18:09:38 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:38 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:39 orca kernel: Buffer I/O error on device sdb1, logical block
51727844
Jan 21 18:09:39 orca kernel: lost page write due to I/O error on sdb1
Jan 21 18:09:40 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:44 orca last message repeated 9 times
Jan 21 18:09:46 orca kernel: EXT3-fs error (device sdb1): ext3_free_branches:
Read failure,
inode=25034766, block=51519664
Jan 21 18:09:48 orca kernel: Aborting journal on device sdb1.
Jan 21 18:09:50 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:51 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:51 orca kernel: EXT3-fs error (device sdb1) in
ext3_reserve_inode_write: Journal has
aborted
Jan 21 18:09:51 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:51 orca kernel: EXT3-fs error (device sdb1) in ext3_truncate:
Journal has aborted
Jan 21 18:09:51 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:51 orca kernel: EXT3-fs error (device sdb1) in
ext3_reserve_inode_write: Journal has
aborted
Jan 21 18:09:51 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:51 orca kernel: EXT3-fs error (device sdb1) in ext3_orphan_del:
Journal has aborted
Jan 21 18:09:51 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:51 orca kernel: EXT3-fs error (device sdb1) in
ext3_reserve_inode_write: Journal has
aborted
Jan 21 18:09:53 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:53 orca kernel: EXT3-fs error (device sdb1) in ext3_delete_inode:
Journal has aborted
Jan 21 18:09:54 orca kernel: sd 2:0:0:0: rejecting I/O to device being removed
Jan 21 18:09:54 orca kernel: ext3_abort called.
Jan 21 18:09:55 orca kernel: EXT3-fs error (device sdb1):
ext3_journal_start_sb: Detected aborted
journal
Jan 21 18:09:55 orca kernel: Remounting filesystem read-only
Jan 21 18:09:55 orca kernel: __journal_remove_journal_head: freeing
b_committed_data
Jan 21 18:10:00 orca last message repeated 10 times
=======================
So my main question is: is it a hardware problem with the laptop or lack of
support for my
hardware in Linux?
Thank you,
Igor
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
