Error extracting zip larger than 4 gigabyte

[heberpimentel]

Good Morning,
I generated a 12 gigabyte zip, and can't extract the files on windows and linux.
Depending on the size of the zip, I can extract but lose data. This from 4 gigabyte.
zipParameters = new ZipParameters();
zipParameters.setEncryptFiles(true);
zipParameters.setEncryptionMethod(EncryptionMethod.AES);
zipParameters.setAesKeyStrength(AesKeyStrength.KEY_STRENGTH_256);
zipParameters.setCompressionLevel(CompressionLevel.NORMAL);

[heberpimentel]

A note: I can extract using zip4j but not with linux and windows applications. If I zip with windows or linux applications, it works normally.

[nicolabeghin]

this could depend on the app you're using to extract, since with such big size zip4j should automatically use ZIP64 in place of standard ZIP

[heberpimentel]

I have used 7zip or 7z and not used unzip

[heberpimentel]

Do you have any recommendations for a program so I can do some more testing? Sorry for English'

[nicolabeghin]

AFAIK 7-zip supports ZIP64 so I don't see a reason why it shouldn't work.. @srikanth-lingala any hint on this?

[LeeYoung624]

No doubt that Zip64 is working in your use case. Considering the size of the zip file, asking you to provide the zip file is a bad idea.

Please allow me to make it clear:
You are trying to zip 12 GB files into a zip file using zip4j. You can only extract the zip file generated by zip4j when using zip4j, not 7zip/unzip. When you zip these file using other libraries like 7zip, it could be extracted by zip4j and 7zip. Am I right?

[srikanth-lingala]

@heberpimentel @nicolabeghin I will try to reproduce this and update the thread. We have tests here for Zip64 format, but the zip file is created and extracted by zip4j, and if I understand correctly, the issue comes when the huge zip file is created with other tools.

[heberpimentel]

@srikanth-lingala it's the opposite ... I'm generating with zip4j, and trying to extract with other programs

[srikanth-lingala]

Thanks for correcting me.

[srikanth-lingala]

Fixed in v2.2.1