I can now repeat my rsync download corruption. If a local file has size differing from the archive (ftp1.sourceforge.net) filesize, then the download gets corrupted, otherwise a new file is downloaded correctly.
Here is an example. Initially, I have 82427 Jan 31 03:01 Packages.gz The ftp1.sourceforge.net has size 64,902 . I run the commandline download, rsync -vt rsync://ftp1.sourceforge.net/debian/dists/woody/non-free/binary-i386/Packages.gz Packages.gz which produces the error message, Warning: unexpected read size of 0 in map_ptr I infer that this isn't directly an "rsync" problem, but rather an underlying library that does the "map_ptr" into the file. I use rsync version 2.5.1-0.1 [which requires libc6 version >=2.2.4-4] libc6 version 2.2.4-7 I suppose I should figure out where "map_ptr" comes from, but I suspect that would take me a half day since I am unfamiliar with the tools to find its source. Any ideas where "map_ptr" comes from and if/how I might correct it? Thank you, Jameson Burt On Thu, 31 Jan 2002 02:39:11 Jameson Burt wrote: > I use "rsync" to mirror most of i386 Debian Linux. > This has worked well for a year until the last few days. > I tried to correct some oddly working packages that I had recently upgraded, > but apt-get noticed that the locally downloaded Packages.gz files were > corrupted, > which I affirm by hand, > gunzip: Packages.gz: invalid compressed data--format violated > > > Checking the source of the Packages.gz files, I used a command line rsync for > one file, > rsync -vt > rsync://ftp1.sourceforge.net/debian/dists/woody/main/binary-i386/Packages.gz > . > This downloaded Packages.gz that "gunzip" could unzip. > For example, dists/testing/non-free/binary-i386/Packages.gz had length > 64,902 > However, before my single file rsync, my nightly batched-rsync Packages.gz > size was 88,035. > Restarting the batched-rsync, the new Packages.gz became 81,726 which is > still not correct. > However, if I remove Packages.gz from my archives, then a batched-rsync > downloads Packages.gz correctly with 64,902 bytes. > > Of course, I don't know how long I have had this underlying problem. > I first noticed it this week. > Could this be a problem with "rsync" or were there kernel problems so my > filesystem is going bad, or ...? > Any ideas? > > > I run the following (though installation corruptions have evidently occurred > lately), > kernel version 2.4.12 with all ext2 filesystems > Debian version 3.0, though I haven't upgraded about 400 changed packages > in the last 3 weeks > libc6 version 2.2.4-7 > dpkg version 1.9.18 > gzip version 1.3.2-3 > > Thanks, > Jameson Burt > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
