Le 24.07.2014 15:19, Eduardo M KALINOWSKI a écrit :
On Qui, 24 Jul 2014, berenger.morel wrote:So, I wonder if there is a way to fix this inode's size repartition? In a more general way, if people have some advices about that kind of issues (choosing the right cluster and partitions size, the right partition format, etc depending on the planned usage)? I know, those questions (and the error I supposed I made) may seem trivial for real administrators, but... I'm a simple programmer, not an admin.It's not possible to change the number of inodes after the filesystem has been created. You'll have to backup and create a new filesystem.
As I feared.
As far as I remember, I've always accepted the defaults for number of inodes, and I've never got even close to exhausting inodes.
First time I have exhausted inodes, but I never used apt-cacher-ng previously, and it's quite obvious that a proxy+cache is very greedy in terms of inodes. The nice thing here is that I have learned a lot of this error, and maybe someday I'll be able to help someone else in a similar situation, or be able to understand better partition systems.
One of my defects is that I always try to tweak things... (with time I've learned to not do that when the target is very important) but at least it allows me to learn. By failures :)
-- Eduardo M KALINOWSKI eduardo@kalinowski.com.br