Hi,

I have a compressed log file which gets restarted everyday and starts a new log i.e. todays log file 21072017.bz2.

I need to take a snapshot of the active log file and copy it to another directory in order to decompress and view the file contents.

so I copied the file to /temp

when I then run bzip2 -d 21072017.log.bz2 I get the following:


bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: No such file or directory
Input file = 21072017.log.bz2, output file = 21072017.log

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

bzip2: Deleting output file 20170721.log, if it exists.

Any help on how I can hot copy or snapshot this file please would be great.

Try this or

Symlinks to the same program - unlikely to make a difference.

@ridemeve2017 are you saying this file is continually being written to ?.

Yes the file is always being written to for a 24 hour period. A new log file is created every 24 hours.

I'm not seeing bunzip2 or bzcat as symlinks. If the log file is running through a bzip2 process, and it is never quite finished, then using the dd method above to uncompress it as a bit stream may work. the bzip2 program has a lot of checks in it with multiple different options. I don't think bunzip2 and bzcat pay any attention to those.