write error (disk full?).

[ashley75]

I am trying to unzip a file and I got the following error:


inflating: region.dbf
region.dbf: write error (disk full?). Continue? (y/n/^C)


the weird thing is that I have plenty of space on the location I unzip the file to. Below is infor about space on my server:

Filesystem Size Used Avail Use% Mounted on
/dev/sda8 1.1G 183M 865M 18% /
/dev/sda1 30M 20M 9.5M 67% /boot
/dev/sda5 3.7G 2.4G 1.1G 67% /home
none 314M 0 314M 0% /dev/shm
/dev/sda9 494M 8.1M 460M 2% /tmp
/dev/sda3 8.6G 3.2G 5.0G 39% /u01
/dev/sda2 16G 14G 1.9G 87% /u02
/dev/sda6 1.7G 1.6G 139M 92% /usr
/dev/sda10 243M 47M 184M 21% /var

I unzip the file to /u01 and the unzip file I expected is about 2G.

What am I suppose to do to fix this problem????

thanks

 

[pupu]

Are you sure that you are unzipping it there? Try to df while you are in progress of unzipping and see if the capacity changes on the proper disk.

 

[ashley75]

yes I am positive that I unzip to /u01 so that's why I said it's weird.

 

[stanhubble]

your target maybe in /u01 but could a temp file be created in /tmp or /usr/tmp.

 

[bluegroper]

/usr looks quite full.

 

[tarn]

My guess is that unzip is creating a temporary file as it unzips the archive and is filling where ever that temporary file resides.

Try a "man unzip" (or whatever archive tool you are using) it may be that you can set a flag to use a different temporary directory while you extract.

Good Luck

Laurie.

 

[PcLinuxGuru]

What are you using to unzip the file?

 

[idsp]

I also am getting this same error on a large file compressed in a .zip archive. This particular .zip file is only about 600MB large however it contains a compressed rootfs that is over 3GB in size.

It errors on the same file and always at the same size (2.1GB) during extraction before the error causes the unzip to halt (see below)

The zip files md5sum is fine and the file extracts without any errors under WindowsXP (go figure) using WinRAR but under debian Linux (2.4.20) with plenty of space all around I get:

>unzip Gentoox.ShALLaX.Home-Edition-v2.0.zip
Archive: Gentoox.ShALLaX.Home-Edition-v2.0.zip
inflating: Gentoox.ShALLaX.Home-Edition-v2.0/gentooxx.xbe
inflating: Gentoox.ShALLaX.Home-Edition-v2.0/initrd.gz
inflating: Gentoox.ShALLaX.Home-Edition-v2.0/linuxboot.cfg
inflating: Gentoox.ShALLaX.Home-Edition-v2.0/READMEv2.txt
inflating: Gentoox.ShALLaX.Home-Edition-v2.0/rootfs
Gentoox.ShALLaX.Home-Edition-v2.0/rootfs: write error (disk full?). Continue? (y/n/^C)

>ls -al
total 2100792
drwxr-xr-x 2 root root 4096 Jun 10 11:11 ./
drwxr-xr-x 3 pubrw dhstaff 4096 Jun 10 10:52 ../
-rw-rw-rw- 1 root root 9607 May 24 18:21 READMEv2.txt
-rw-rw-rw- 1 root root 1323832 Mar 30 22:08 gentooxx.xbe
-rw-rw-rw- 1 root root 264817 May 24 23:46 initrd.gz
-rw-rw-rw- 1 root root 99 May 19 15:57 linuxboot.cfg
-rw-r--r-- 1 root root 2147483647 Jun 10 11:12 rootfs

Always rootfs causes a halt of unzip process when it reaches 2147483647 bytes in size

Here is the info on the zipfile

>zipinfo Gentoox.ShALLaX.Home-Edition-v2.0.zip
Archive: Gentoox.ShALLaX.Home-Edition-v2.0.zip 627762913 bytes 7 files
-rw-rw-rw- 2.0 fat 1323832 b- defX 30-Mar-03 22:08 gentooxx.xbe
-rw-rw-rw- 2.0 fat 264817 b- defX 24-May-03 23:46 initrd.gz
-rw-rw-rw- 2.0 fat 99 t- defX 19-May-03 15:57 linuxboot.cfg
-rw-rw-rw- 2.0 fat 9607 t- defX 24-May-03 18:21 READMEv2.txt
-rw-rw-rw- 2.0 fat 3145728000 b- defX 24-May-03 16:16 rootfs
-rw-rw-rw- 2.0 fat 268435456 b- defX 22-Apr-03 03:17 swap
-rw-rw-rw- 2.0 fat 935166 b- defX 24-May-03 17:39 vmlinuz
7 files, 3416696977 bytes uncompressed, 627762233 bytes compressed: 81.6%

Everything is happening on /dev/md0 (including /tmp which is symbolically linked into there) so I do not believe it to be an issue with temporary files. Perhaps we should discuss this with the developers of the the unzip program?

>df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 2.0G 1.1G 859M 56% /
/dev/hda7 18G 103M 17G 1% /usr/local
/dev/hda8 159G 802M 150G 1% /home
/dev/md0 949G 568G 334G 63% /mnt/md0
/dev/md1 935G 737G 150G 83% /mnt/md1

You can even try replicating this error on your own by downloading the file from the Gentoox project at

http://gentoox.shallax.com

 

[MrSnipe]

I had this problem and spent half a day trying to figure it out. Here's a simply workaround. I used WinZIP on a Win 98 machine. In the case of the gentoox.zip file, if you try to extract rootfs it will report an 'invalid parameter' error after a few minutes of processing. Not to worry...just check the C:\windows\temp directory (or whatever your temp directory path is) and you should find the rootfs fully intact (check its properties to be sure the file size is 3+ gigs ). Not sure what the problem is with unzip process; it creates the file just fine, but fails to move it to its final destination.

 

[KenCunningham]

idsp - it's strange that your unzip fails at 2.1 Gb. Is your filesystem largefile enabled?

 

[bull3t]

ZIP is limited by filesize.
I forget what the cieiling is, and I have had a few drinks tonight..

Questions:
1) where did the zip file originate from?
what utility was used to create the zipfile you are trying to extract?

2) What utility are you using to extract those files?
Is the extracted file going to be over 1G by itself?
I would say that is a flag. ZIPfiles are limited.
The creator should have used tar or cpio instead

3) what utility are you using to extract those fiels?
is is "unzip"? .. Or your KDE environment (whatever it uses)..
It may use a temp space (see responses above).