-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-02-26 at 23:55 +0100, Istvan Gabor wrote: ...
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.
I thought of that... but as I have never experienced it, I didn't recognize the symptoms. I discarded the posibility <:-}
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.
It is possible to adjust the inode ratio, in Yast, or manually: mke2fs - create an ext2/ext3 filesystem ... -i bytes-per-inode Specify the bytes/inode ratio. mke2fs creates an inode for every bytes-per-inode bytes of space on the disk. The -N number-of-inodes overrides the default calculation of the number of inodes -T fs-type Specify how the filesystem is going to be used, so that mke2fs can chose optimal filesystem parameters for that use. The supported filesystem types are: news one inode per 4kb block largefile one inode per megabyte largefile4 one inode per 4 megabytes But I would simply switch to reiserfs. You said:
As the freedb database contains zillions of small files it
That's perfect for reiserfs. Ideal for you ;-) At least, try, I'd like to know if the untarring runs faster on reiserfs under the same conditions - I'm very curious, it should be much faster ;-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEAx6atTMYHG2NR9URAh2AAJ9O5V0mBTLDJV/fwXDSQ+EClJuNDQCfTyUa HfgaPb15TCGRxq+wsVcZJXA= =8oa4 -----END PGP SIGNATURE-----