(sent again, I don't know what happened with the previous mail) Dear all:
I have to copy 500GBs from an external lacie usb drive (NTFS) to my HD. When I started I noticed that the thing was veeery slow (USB 1.x, around 1mb/s) so I asked my ISP to add a USB 2.0 card on my server (Dual Xeon 2.8, 1gb ram, Debian Stable running 2.4.26-686-smp). After they installed the new card I found that NTFS entered in some infinite loops when doing a recursive copy from the USB drive to the HD and I couldn't access all the files on the disk. When reading the logs, I saw that the errors where NTFS related (it sounded rare to me, since the NTFS driver was the same, the only difference was the USB card) so I had a conversation with linux-NTFS people. After some tests, they pointed out that probably the problem was USB related (http://sourceforge.net/forum/forum.php?thread_id=1106787&forum_id=44085). Some info about the hardware and software on the server: Before upgrading the hardware to USB 2.x I had this USB devices 00:1d.0 USB Controller: Intel Corp.: Unknown device 2482 (rev 02) 00:1d.1 USB Controller: Intel Corp.: Unknown device 2484 (rev 02) 00:1d.2 USB Controller: Intel Corp.: Unknown device 2487 (rev 02) This is the new card installed on the server: 02:01.0 USB Controller: Acer Laboratories Inc. [ALi] M5237 USB (rev 03) 02:01.3 USB Controller: Acer Laboratories Inc. [ALi]: Unknown device 5239 (rev 01) and I was running kernel 2.4.26. Then, the guys from linux-ntfs asked me to upgrade to kernel 2.6.x and I installed 2.6.6-686-smp. Some things changed, since when I was running 2.4.26 I could only list recursively only 2 dirs and now, find printed around 10 dirs before entering in an infinite loop. Then, I installed kernel 2.6.7 (from kernel.org not debian's) to see if things go better but it was the same as 2.6.6. People from linux NTFS thought it was a bug on their code so they asked me to see if I could send some bytes from the disk to analyze them (http://sourceforge.net/forum/message.php?msg_id=2660915) and this is their answer (http://sourceforge.net/forum/message.php?msg_id=2661050): " Apparently you have a USB 2.0 problem. The data you sent are totally OK now. If it's compared with the wrong one, the bytes start to differ at exactly position 256 (often used as a unit during data transfers). Something messes up things randomly before they would arrive to the NTFS driver. " I would love to help you to fix this problem. I have full access (remote) to the machine and it's not yet in production enviroment so we can boot it the times we need. Any ideas? Thanks in advance ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
