0

I have a gzipped file that Ubuntu reports is 2,119,952,848 bytes in size. When I try to gunzip on a mount with 12GB free space, I get the error "No space left on device".

Here's where it gets really strange... the file is a compressed mysqldump so should be highly compressible. However, gzip reports a large negative compression ratio:

ubuntu:/mnt/tmp$ gzip -l my.sql.gz
         compressed        uncompressed  ratio uncompressed_name
         2119952848          1471106218 -44.1% my.sql

Any idea what might be going on with this?

  • Can you give the gzip version? "gzip --version" and your architecture (32 or 64 bits) ? – Weboide Jun 21 '10 at 21:50
3

May be the uncompressed counter is only 32 bit and so it reset to this wrong value

| improve this answer | |
1

Try to verify size of uncompressed data:

gzip -dc my.sql.gz | wc

If it will be smaller than your free disk size - check limits/quota.

| improve this answer | |
0

Could be:

  • The file system /mnt/tmp only supports file sizes up to 2GB.
  • /mnt/tmp really is running out of space (gunzip -c FILE | wc -c will show you the uncompressed size)
| improve this answer | |
0

could be inodes! df -i

| improve this answer | |
0
  1. What about the root "reserved" area on the disk? Depending on how this is accounted for in df, some of your empty space might not be available to you and reserved to the root user.

  2. Another issue is that the compressed file is not released and deleted until the uncompression is complete. Your partition might not be able to hold both of these with the amount of space you have available.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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