Skip to content

Out of inode limit on 'unlimited' plan

Reviews Locked by pieter_rtm 7 replies 761 views
This thread is locked — new replies are not accepted. (Thread ran its course)
#1

To be honest, "unlimited" never is. Hetzner's GreenCloudVPS-branded "unlimited" shared plan. Specs as tested:

  • 100 GB SSD storage
  • "Unlimited" bandwidth
  • Inode limit: 250,000 (buried in AUP section 14.3)
  • My usage: 247,891 inodes

Discovered when WordPress updates failed. Error log: "No space left on device." df -h shows 67% disk used. The limit is invisible until you hit it. As said, this is standard industry practice, but the marketing is aggressive. I need this site running by Thursday. Has anyone successfully negotiated a limit increase, or do I compress/merge and pray?

Containers before it was cool
#2

Asking for a friend who values privacy over promises.

#3
pieter_rtm said:
Specs as tested: 100 GB SSD storage "Unlimited" bandwidth Inode limit: 250,000 (buried in AUP section 14.3) My usage: 247,891 inodes...

I try df -i but not work? Is there easy way to find big folder? My site is small but limit hit?

builds at 3AM, sleeps at noon
#4

I got this reply when I hit the inode limit on my 'unlimited' plan:

  • The inode allocation is documented in their Acceptable Use Policy
  • The "unlimited" designation refers to bandwidth, not file system objects
  • Current plan inode limit: 250,000
  • Upgrade path available to Business tier: 500,000 inodes

They told me to open a ticket for migration assistance. Not the clearest thing I've ever read.

1 #5

Just use `find. -xdev -printf '%h\n' | sort | uniq -c | sort -k 1 -n` and pipe to head skill issue is not reading the AUP before signing

Also 500k tiny files from failed WP installs? Buddy that's not "unlimited" that's "unlimited regret"

oops: 0000 [#1] SMP
#6

250k inode "unlimited" lol I seen worse on HostHatch but still

builds at 3AM, sleeps at noon
#7

AUP section 14.3 they always bury it deep

#8

Skill issue indeed

Thread closed

Replies are closed on this thread. Thread ran its course.