From: [email protected]

Thanks for submitting this, Dariush.

I've confirmed this bug with a 2.1GB file and a 1.9GB file, so it
probably isn't a problem with large file support in the
kernel/filesystem. I had a discussion with my sponsor about using -O3
(the author's setting) versus -O2 (perhaps less likely to break
stuff). I recompiled with -O2 and tried again, but that didn't remedy
the situation.

Those two I used were sparse files (from /dev/zero). However, a 1GB
sparse file (also courtesy of /dev/zero) worked as expected.

So then I tried a 2GB file from /dev/urandom, still with the -O2
compiled rzip. No problems. Seems your intuition was right about the
sparse file issue. I don't have access to a machine now I can test
out a file your size on, but I'm guessing that a 6GB-ish file created
from /dev/urandom will compress and decompress properly.

I'll poke around in the code and see if I can fix this, but I may need
to forward this upstream. I won't be able to get to that until
sometime next week, though.

Alec

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBGyziAud/2YgchcQRAoV1AJ45ar1pID3Z9TecuME283dSVUC3MACfQNAh hIEGGf2Z/00ymWB+Fs3NMk4=
=8V+u
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)