XF 2.3 Too many inodes

[airgunforums]

Ok my server has told me I have too many
I have about 2,500,000
I’ve looked at where and my issue seems to be attachments
I have internal data attachments and data attachments
Now obviously these are duplicates of each other in theory
And I have 920 folders in each and each folder contains upto 1000 files
Any ideas on how I can resolve my issues as this is obviously the main cause of it

 

[mjda]

As far as I know there wouldn't be a way to resolve this within XF, without deleting some of your attachments. Your best bet is to request an increase from your hosting provider, upgrade your hosting to something with more inodes, or switch hosting completely.

 

[briansol]

Move your attachments to s3/R2/spaces. It's really the best thing you can do for yourself.

 

[mjda]

Move your attachments to s3/R2/spaces. It's really the best thing you can do for yourself.

Great suggestion right here. I actually use S3 myself and didn't even consider that to be something I suggested. Old age is no joke y'all!

 

[Anthony Parsons]

Ok my server has told me I have too many
I have about 2,500,000

Are you on shared hosting? That could be the only instance I could think would have such a low limit, as an OS has billions of inodes available. Honestly, it is cheap to just use a VPS, which would solve that issue. Not sure what you use, but if you need to transition to a VPS, I can help you out. Retired and always looking for things to do.

 

[airgunforums]

thanks for suggestions
i looked at vps but with having 1.5tb of files etc a vps would not be affordable till i reduce some size

 

[Anthony Parsons]

thanks for suggestions
i looked at vps but with having 1.5tb of files etc a vps would not be affordable till i reduce some size

Have you thought about hosting your attachments in S3? Cheap storage hosting and you're only paying a small price for the actual data transfer of pages being viewed loading images in content currently visited. Very little old, stale, content would be loaded.

You could leave your hosting as is, unload your 1.5TB attachments to S3 and then just pay the tiny storage cost and whatever the actual bandwidth cost is. Not sure if you have looked at that option. That would remove your inode issue and the huge local storage cost on a VPS or such.