You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title large file check not happening when scanning ftp.uni-muenster.de
Priority bug Status resolved
Superseder Nosy List ant, poeml
Assigned To Keywords scanner
In November 2008 I observed that the scanner didn't do the "large file check" that it
is supposed to do for files > 2GB, when it scanned the University of Muenster mirror.
The rsync server says hello with "@rsyncd: 30.0", which means it's not an old one.
What's worse, I see that the same "broken" length (-1) comes from other mirrors, like ftp5.gwdg.de. So
we have a serious bug here that probably affects all mirrors running rsync 3.x (which were few, two
years ago, but now should be most).
I was fooled -- it is only the display of the number which was broken. I fixed
this in trunk (r8230).
Regarding the actual bug, I cannot reproduce it anymore: the large file check
happens correctly with that mirror. I'll assume that something has been changed
there and close the bug.
History
Date User Action Args
2010-11-14 17:27:34 poeml set status: deferred -> resolved
messages: + msg313
2010-11-14 16:49:17 poeml set messages: + msg312
2009-12-07 03:16:13 poeml set status: unread -> deferred
2009-12-01 20:55:19 poeml set keyword: + scanner
2009-11-04 16:33:50 ant set nosy: + ant
2009-10-07 20:40:18 poeml create
(end of migrated issue)
The text was updated successfully, but these errors were encountered:
Issue migrated (2015-06-05) from old issue tracker http://mirrorbrain.org/issues/issue8
msg20 (view) Author: poeml Date: 2009-10-07.20:40:18
In November 2008 I observed that the scanner didn't do the "large file check" that it
is supposed to do for files > 2GB, when it scanned the University of Muenster mirror.
(Reported in the openSUSE bug tracker at the time, and now moved here.
https://bugzilla.novell.com/show_bug.cgi?id=445831 )
I supposed that something is special about that mirror that prevents the check from
happening; for all other mirors it seemed to work.
msg312 (view) Author: poeml Date: 2010-11-14.16:49:16
This is probably why:
mb scan -d distribution/11.3/iso muenster -vv
[...]
ftp.uni-muenster.de: rsync ADD: 644 -1 Wed Jul 7 11:33:29 2010
distribution/11.3/iso/openSUSE-11.3-DVD-x86_64.iso
ftp.uni-muenster.de: rsync ADD: 644 189 Thu Jul 8 11:01:22 2010
distribution/11.3/iso/openSUSE-11.3-DVD-x86_64.iso.asc
ftp.uni-muenster.de: rsync ADD: 644 63 Sun Jul 11 07:36:12 2010
distribution/11.3/iso/openSUSE-11.3-DVD-x86_64.iso.md5
ftp.uni-muenster.de: rsync ADD: 644 71 Sun Jul 11 07:38:53 2010
distribution/11.3/iso/openSUSE-11.3-DVD-x86_64.iso.sha1
ftp.uni-muenster.de: rsync ADD: 644 343117 Thu Jul 8 10:58:43 2010
distribution/11.3/iso/openSUSE-11.3-DVD-x86_64.iso.torrent
ftp.uni-muenster.de: rsync ADD: 644 716177408 Tue Jul 6 09:44:46 2010
distribution/11.3/iso/openSUSE-11.3-GNOME-LiveCD-i686.iso
[...]
The rsync daemon, or the scanner, report the file size of the DVD as -1. D'oh!
Using a real rsync client, the output does not look suspicious:
rsync --no-motd rsync://ftp.uni-
muenster.de/ftp/pub/linux/distributions/opensuse/distribution/11.3/iso/openSUSE-11.3-DVD-i586.iso
-rw-r--r-- 4346398720 2010/07/07 11:11:08 openSUSE-11.3-DVD-i586.iso
The rsync server says hello with "@rsyncd: 30.0", which means it's not an old one.
What's worse, I see that the same "broken" length (-1) comes from other mirrors, like ftp5.gwdg.de. So
we have a serious bug here that probably affects all mirrors running rsync 3.x (which were few, two
years ago, but now should be most).
msg313 (view) Author: poeml Date: 2010-11-14.17:27:32
I was fooled -- it is only the display of the number which was broken. I fixed
this in trunk (r8230).
Regarding the actual bug, I cannot reproduce it anymore: the large file check
happens correctly with that mirror. I'll assume that something has been changed
there and close the bug.
(end of migrated issue)
The text was updated successfully, but these errors were encountered: