search for: b32768

When using the -z and -B65536 options together, sometimes there is file corruption. Client and server are both compiled against zlib 1.1.4, so the gzip corruption shouldn't be there, right? With -z and -B32768 there is an error, but it is detected in a different way. With -B65536 and without -z all seems to be going OK. With -B16384 and with -z all seems to be going OK. I'm guessing this is not a protocol limitation of rsync since it works OK without -z, but maybe it is problem in chunk sizing with...

...in e2fsck -which now is solved, I upgraded to 1.39, but now I have hit another problem (on another partition): The partition was formatted as ext3, and debugfs / dumpfs showed that the feature 'has_journal' was present (as expected). The e2fsck command gave the following: # e2fsck -B4096 -b32768 /dev/hda11 e2fsck 1.39 (29-May-2006) e2fsck: Attempt to read block from filesystem resulted in short read while checking ext3 journal for /var So it seemed like a problem in the journal, as I could not find any option to e2fsck to tell it to skip applying (and reading) the journal, I set the file...