New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
As a consumer, not a provider, is there really any performance interest in setting the inode limit to anything lower than (hard quota)/(disk sector size)?
From what I know, the number of inodes is fixed for an ext partition. So a client, could potentially eat up all the inodes without eating up a lot of space in the data sector. If this is true, then clients that are also using the partition would not be able to create new files.
Without proper Inode limit, a single vps can eat up all the resource without hardly using any disk space. I have a decent limit up for a long time. But just checking what is the industry standard/limit for decent disk space lets say 25Gb.
OpenVZ's new file system, ploop, actually solves this issue. Clients have their own file system, so can not use up your inode limit.
@Daniel if only it was stable...
I'd really like to use ploop too...
Regardless, on our most populated node, we're going to run out of disk space before inodes:
inodes:
disk space:
And that's with standard ext4 allocations
Can't help with original question but @Damian how on earth have you got figures like that?
vs...
@Oliver: Our filesystem is quite a bit larger than your filesystem, so it's not that unusual I guess
Hah my bad, I read your things around the wrong way... Thought you had 2% of the disk used and 18% of the inodes.
facepalm