I am compressing log files daily and very recently I have been seeing some crazy results on the file type of the file after compression.Normally you would expect file filename.gz returning gzip compressed data and some info on the file, but on many files I am seeing just data, raw G3 data, byte-padded, DBase 3 index file random stuff.Any issues anyone could think of that could be causing this? I can't decompress the file then because it is not recognized as a gzip fileIt is really bizarre why this is happeningTo Add: The file also comes up as corrupt in many cases. When doing a gzip -d I either cannot decompress it because it says not recognized or it is actually corrupt. This never happened before, I know it is possible for a file to compress corrupt, but there must be something going on in which the frequency has increased to multiple files a day being corrupt whereas before it wasn't even one a year. 
Erratic behavior with gzip on unix
linux;compression;gzip;data