Hi all, A starnge thing happened while I was rsyncing Debian binary-i386-1_NONUS.iso from ceu.fi.udc.es . At first I made a pseudo-image, then I rsynced it using this:
rsync --verbose --progress --stats --block-size=8192 ceu.fi.udc.es::debian-cd/potato/current-iso-images/binary-i386-1_NONUS.iso . This took more than 12 hours and the progress indicator never came over 2% done. Then I checked md5sum using this: md5sum -b binary-i386-1_NONUS.iso The md5sum differed from that one that appeared in MD5SUMS file. That's why I tryed rsyncing again using this: (I'm not sure about this as I typed it 'over the phone') rsync --verbose --progress --stats --block-size=131072 ceu.fi.udc.es::debian-cd/potato/current-iso-images/binary-i386-1_NONUS.iso . (The directory didn't change) MD5SUMing other two iso was succesfull after first rsync. But this last rsync command is running for > 30 hours as for now and the progress indicator is showing 14% . Can someone please tell me what could be the bottleneck and why the second rsync took longer that the first one. Are there any 2.2r0 binary-i386-1_NONUS.iso 's in Latvia (.lv)? -- Mail You Later! Aigarius [EMAIL PROTECTED] ----------------------------------------------------------------------- Origin: Not enough hard drive space... please delete windows. PLEASE!!! ----------------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]