Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When performing a tar on a bz2 compressed file I am encountering the following error,

tar: dump.sql: File shrank by 19573448400 bytes; padding with zeros

Can anyone point what might be causing this issue ?

Thanks.

share|improve this question

It's not an error. It's INFO.

I'm willing to bet you're compressing/decompressing a Virtual Machine image, or otherwise sparsely-allocated file.

Bzip2 has detected that the file is mostly zeroes, and compressed it so that they're not there in the compressed file.

This is the difference between actual size and apparent size of sparse files.

share|improve this answer
    
I found a thread that helpfully corroborates and further explains: groups.google.com/d/msg/comp.os.linux.misc/RES9Kvw7kO4/… – Martin Eden Jul 14 '14 at 10:57
    
If it's not an error, then why does it produce a non-zero exit code? – Ben Collins May 12 at 2:34

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.