Bugzilla – Bug 131609
Cannot copy large files from USB-connected hard disk.
Last modified: 2006-03-08 07:19:28 UTC
When trying to read a large file from a usb-connected hard disk, the file copy fails after 3.4MB copied. This has been verified on: Suse 10.0 RC4 using the "Rescue System" Suse 9.3 using the "Rescue System" Suse 9.3 ater booting into the normal system boot. Note: It is possible to copy a large file to the USB-connected hard disk but not to read it back. This bug has been checked on Ubuntu 5.04 and is NOT present in Ubuntu 5.04.
Sorry my fault, It is late. I'm under heavy workload but bugzilla will not forget. This is not a usability bug but a hardware device bug. Is it still alive. Did you test it with a SL 9.1 beta? Can I close the bug?
This is not a hardware bug, as the bug is NOT present under Ubuntu 5.04 as was noted in the original bug report. We have not tested under Suse 9.1 beta. This bug should not be closed before it is fixed.
I meant "a SUSE bug during use of this hardware device" ;-) Dear screening team, is USB part of the component base system? John: can you provide a hw-info report? Thx.
Created attachment 67717 [details] hw-info as requested Feb 10th 2006. This is the hw-info generated for the system. Notes: 1) The USB-connected hard disk referenced in the original report "storage_model_OneTouch_II" is connected and turned on but does not have an ext2 partition on it. It has been converted to ntfs for other uses. 2) The IP address of the system has been obfuscated. The reported problem occurred when there was an ext2 partition on this external hard disk "storage_model_OneTouch_II" and we found we could not read large files (> 3.4MB) from that partition. Thanks to all for your hard work on solving this problem!
John: You actually mean 3.4M, not G? I really think this is hardware specific. Siegfried: With USB, Danny Kukawka is a good point to start as these devices are getting managed by HAL ;)
3.4 Megabytes is correct. Please note that the same USB hard disk worked fine on the same server with Ubuntu 5.04, as described in the original bug report. I suspect that this proves beyond any doubt that this is not a hardware problem. JS
How was the device mounted? By hand or automatically? Please attach the related part of /proc/mounts for the device. Any messages in /var/log/messages?
Sorry, that info is not available. The system has been redeployed. Previously, I attached the hw_info output that I got just before the system went out the door.
I can't say anything in this case. Btw. If there is a problem with copy file from USB storage, this is a kernel problem and not related to HAL.
What is the failure mode with you "can not copy the file"? Are there any kernel error log messages? And this was with ext2, not ntfs, right? Also, does 10.1 beta 3 work properly with this hardware?
Please provide feedback, else we will have to close this bug,
No feedback, which probably means it's fixed or went away otherwise