| 1 |
On 12.12.2011 15:54, Alex Schuster wrote: |
| 2 |
> Joseph writes: |
| 3 |
>> That is scary. I just install new HD with 2TB capacity and ext4 that is |
| 4 |
>> 2% full and: |
| 5 |
>> $ find /home/joseph/ -xdev | wc -l |
| 6 |
>> shows: 169977 that is 26% full. |
| 7 |
> No, that is 26% of the number of total inodes _Daniel_ has on his small |
| 8 |
> partition. Yours is bigger, so you have more inodes. My largest partition |
| 9 |
> has 724G, and 46 million inodes. Use df -i to see how many you have. |
| 10 |
Ah yes... My partition is only 10GB, and mkfs.ext4 sais in its man page |
| 11 |
(at "-N" option) it uses a "calculation [..] based on the number of |
| 12 |
blocks and the bytes-per-inode ratio". So a small partition will have |
| 13 |
fewer inodes than a big partition. |
| 14 |
|
| 15 |
mkfs.extX uses settings for the inode-block-ratio from /etc/mke2fs.conf. |
| 16 |
The "-T" option configures which one to use, my partition falls into |
| 17 |
category 512MB < "default" < 4TB, which makes it use inode_ratio=16384. |
| 18 |
I think I should use the "news" type. It has inode_ratio=4096, which |
| 19 |
should give me 4 times the inodes.... testing... yes: 2621440 inodes |
| 20 |
instead of 655360. |
| 21 |
|
| 22 |
Previously I used reiser3fs for this kind of filesystem usage, but it's |
| 23 |
not faster than extX anymore. Moreover it's running on a SSD now, and |
| 24 |
afaik reiser3fs doesn't support TRIM :( |
| 25 |
|
| 26 |
OK - thank you all. It seems I'll have to reformat. |
| 27 |
|
| 28 |
Bye, |
| 29 |
Daniel |
| 30 |
|
| 31 |
-- |
| 32 |
PGP key @ http://pgpkeys.pca.dfn.de/pks/lookup?search=0xBB9D4887&op=get |
| 33 |
# gpg --recv-keys --keyserver hkp://subkeys.pgp.net 0xBB9D4887 |
Archives