Even if I exceed --bwlimit 300, the transfer speed still sticks around 300. It may be that rsync works because it is sending data in smaller packets than the software for the device.
In fact, by patching the software for the device to copy data to the device in 1K blocks, I'm usually able to avoid crashing/locking up. The software was trying to copy in 1M blocks. I could experiment with the block size, if that would be enlightening. I can also try to do some more tests with various rsync settings to see if I can narrow it down any more... --Adam On Wed, Jul 09, 2003 at 04:30:11PM -0700, Matthew Dharm wrote: > Have you done any testing to determine the maximum bwlimit setting which > works? > > On Wed, Jul 02, 2003 at 01:15:36PM -0400, Adam Kessel wrote: > > I got some advice from someone else experiencing this problem to use > > rsync --bwlimit, which actually works. > > > > If I set the bwlimit around 300 kbps for the transfer, I'm able to fill > > the device to capacity without hanging my system. > > > > Does this mean that the device isn't telling the usb system when it can't > > "take anymore"? Does this help narrow the problem to a usb vs. firmware > > problem? From what little I understand of this stuff, it seems like maybe > > when the device's buffer is full linux doesn't know to stop sending data.
pgp00000.pgp
Description: PGP signature
