but I got this error message:
mkdir sda4/temp mkdir: cannot create directory `sda4/temp': No space left on However df -h shows the same as above: df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 9.2G 4.9G 3.9G 56% /home/user/sda4
Now I don't know what the problem is and how I could fix it.
I've asked a friend who knows linux better. He suggested checking if there is enough free inodes in the file system. As the freedb database contains zillions of small files it can happen that the number of files greater than the inodes available on the filesystem even if the physical size of all the files is less than the free space on the partition. If the filesystem runs short of free inodes new files can't be created, similarly to when the partition is full. I checked the inodes: df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sda4 1221600 1221600 0 100% /home/user/ sda4 As you can see it happened exactly what he supposed. All the inodes are used. That caused the problem. 10 GB place should be enough nevertheless. The question now is how I can set up the partiton so that the same size would have more inodes. To Per Jessen: Uncompressing the bz2 file does not take a long time. But untaring takes hours. I have untared the 3.2 GB tar file again on a 20 GB partiton. It took 20 hours to finish on my system (AMD sempron 2200+, 512 MB RAM, SATA1 HD). The final space that the whole stuff occupies is 7.5 GB. Thank everybody for helping! IG ___________________________________________________________________________ [origo] klikkbank lakossági számlacsomag havi 199 Ft-ért, bankkártya éves díj nélkül! www.klikkbank.hu