I have never been a Microsoft fanatic nor an anti-microsoft terrorist, but today I could not believe that large compressed folders got corrupted in Windows !
I have send a relatively small zip file (5gb, peanuts) from AIX to Windows per sftp and in Windows Explorer, some files in the compressed folder (read zip) were just pointing to the wrong content.
I had some issues with large zip files on unix, but this was last century! Howcome could a modern filesystem/operating system have such issues?
I have found a few bugs on support.microsoft.com.
Ex: Compressed folder becomes corrupted when larger than 2 gigabytes
Workaround : make sure that you limit the size of a compressed folder to 2 GB or less
Amazing!
There are so many 2GB and 4GB boundary bugs in Windows it’s amazing how the platform is still considered a viable enterprise server OS… And yes, that goes for 64-bit Windows as well!
Indeed, the issue was on W2008R2 64-bit !
Built-in zp function in Windows Server 2003 R2 x64 is crappy, too.
You are not able to create a zip file bigger then 2 GB. “Discovered” it when i tried to compress several small RMAN backup pieces a 512MB into one bigger zip file.
So that’s why all those 11g downloads are two files.
Nice point Joel 🙂
Many windows sysadms use 7-zip instead
From
http://en.wikipedia.org/wiki/7-Zip
(go to limitations paragraph)
“… 7-Zip supports file sizes of up to 16 exabytes…”
Thanks for the link. I had no issue with winzip 9 and later. Afaicr, winzip 8 did not support large files and I had to download WZ9 beta, this was about 7 years ago !
7-zip is open source and FAST
@Kennie Nybo Pontoppidan