strange problem with / used space

[Minoia]

It is not a bug.
The root filesystem is full.

Please try to find some big files on / with command find / -xdev -c 10000000c | xargs ll -d

This command list all files bigger the 10MB, please check the list and find the files those have not reason to stay on root file system

[Bill Hassell]

> /dev/vg00/lvol3 1572864 1572784 80 100% /

The root filesystem is full. A LOT of things are going to fail in this situation, not just un-zipping a file.

Do NOT look for big files, look for big directories:

du -kx | sort -rn | head -20

The two largest directories under / should be /sbin and /etc -- nothing else should come close to these directories in size. If so, someone has messed up your root directory. It also appears that you may have root's HOME directory in /, the default location, but a very bad place for root. Check the / directory for junk files (I call them root droppings):

ll / | sort -rnk5 | head -20

Never store large files in root's HOME.

[V. Nyga]

Hi,

> and also this a new installation

So can you repeat the installation?
How full is / then?

Can you 'view' (verbose) the zip file and check for big files?
Can you show us a listing of your zip file?

V.

[Michael Sillers]

I agree with Doug about the kernel allocating disk space. If you are running the unzip command from somewhere in the root filesystem, it may be creating a temporary file there and may still be stuck runnign somewhere in the background.

Since the error occured during the unzip, check to see if it is still running using ps -ef | grep zip.

If it is, kill it then try the bdf command again. That should free up the allocated disk space.

cd to the unzipped directory you mentioned and run the unzip command again to see if there is any difference.