[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On Saturday 02 August 2008 20:15, Anton Channing wrote: > Simon Waters wrote: > > Anton Channing wrote: > >> My webhost is complaining that I have > >> exceeded my inode limit. I never even > >> realised there was such a limit, and > >> certainly didn't know what an inode was. > > > > I think you need to be clear exactly which inode limit. > > > > Older Unix and Linux file systems had a per file system limit, but many > > file systems now have as many inodes as needed (e.g. reiserfs). > > No, I'm on a shared hosting account and the host > claims says that by exceeding 50,000 inodes (I have > between 100,000 and 150,000), I am breaking the > terms and conditions and that they have imposed > this arbitrary limit to 'preserve disk integrity > for the other users'. > > So I can have unlimited domains, but only 50,000 > inodes. Seems like a lot, but many of the CMS > systems I use have thousands of files each. See if you can upgrade them to a DB of some form: that should reduce the count to about 100. In a CMS you shouldn't get much locking. And the backups/migration etc would be a lot easier. Tom te tom te tom -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html