|
#1
|
||||
|
||||
|
Hello,
We have updated the section 7b (Inode usage) in our terms of service. It has come to our attention that some clients are getting worried their account will be suspended due using more then 50,000 Inodes. We DO NOT suspend our clients for inode usage unless they cause problems with our file system, or constantly deleting and recreating large amounts of files which causes high IO usage. ---OLD 7b section--- 7b.) INODES The use of more then 50,000 INODES will result in account suspension. Accounts found exceeding 50,000 INODES will not be backed up on our backup servers. A INODE is the actual file or directory and not the size of that file or directory. For example your index.html file is 1 INODE. A directory called homework is counted as 1 INODE as well. ------ ---NEW 7b section--- 7b.) INODES The use of more than 50,000 inodes on any shared account may potentially result in suspension. Accounts found to be exceeding the 50,000 inode limit will automatically be removed from our backup system to avoid overusage. Every file on your account uses up 1 inode. Simply exceeding the limit does not constitute grounds for suspension however accounts that constantly create and delete large numbers of files on a regular basis or causing file system damage may cause your account to be flagged for review. ------
Last edited by GatorDaveC; 10-08-2007 at 05:56 PM. |
|
#2
|
||||
|
||||
|
Thanks for letting us know. You may want to put "shared and reseller" accounts to prevent confusion to those who don't know that they are one in the same.
__________________
Have a great day, Evan |
|
#3
|
|||
|
|||
|
How do you know if you have reached the limit?
|
|
#4
|
||||
|
||||
|
Create a new PHP files called inodes.php and make sure it is empty.
In it(in code mode and not design) copy this: Quote:
NOTE: Correct me if this is not the right code. Best Regards, |
|
#5
|
||||
|
||||
|
It shows the number of inodes you have in public_html and below.
If you make it something like this it should work: Code:
<?php
system("find /home/USERNAME/ -printf '%i\n' | sort -u | wc -l"); ?>
__________________
quietFinn - netFinn Finland "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." - Dr. Seuss |
|
#6
|
||||
|
||||
|
You should be able to just use the `quota` command to fetch your inode usage which is a lot more efficient then running `find` since the OS already knows your inode count in the quotas.
Code:
quota -u davec
Disk quotas for user davec (uid 32388):
Filesystem blocks quota limit grace files quota limit grace
/dev/sda1 4 629145600 629145600 3 0 0
/dev/sda7 84 629145600 629145600 20 0 0
/dev/sda3 8 629145600 629145600 2 0 0
/dev/sda2 0 629145600 629145600 1 0 0
find | wc -l
20
If you want to get fancy, you can just add all of the Inodes together in all of the file systems by using.. Code:
/usr/bin/quota | /bin/awk '{ if ( $5 ~ /^[0-9]/) total+=$5 } END {print "Total Inodes :" , total}'
|
|
#7
|
||||
|
||||
|
Ok so if you don't have shell access you could make a file named inodes.php and copy/paste these lines to it:
Code:
<?php
system("/usr/bin/quota | /bin/awk '{ if ( $5 ~ /^[0-9]/) total+=$5 } END {print \"Total Inodes :\" , total}'");
?>
__________________
quietFinn - netFinn Finland "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." - Dr. Seuss |
|
#8
|
|||
|
|||
|
Quote:
I just run the scripte by quietFinn & currently do have 43639 inodes, still in the safe margin... BUT!!
__________________
|
|
#9
|
||||
|
||||
|
Quote:
The real difference is that if a reseller account gets suspended, it means that all the accounts under that account (i.e. the reseller's customers) will be suspended too. If you are a reseller and you need to store a lot of files I suggest you don't use your reseller account for that. Better safe than sorry
__________________
quietFinn - netFinn Finland "Be who you are and say what you feel because those who mind don't matter and those who matter don't mind." - Dr. Seuss |
|
#10
|
|||
|
|||
|
thats what I was thinking of !!
On another side tho, I do have a school site which has been online for abt 18 months & that account has 25K in 1 year out of which only 10K in public_html folde (3K is the photos gallery with thumbnails)! I expect the site will grow much larger in this academic year!! any solutions?
__________________
|
|
#11
|
|||
|
|||
|
Thanks for the script quietFinn. Using just a shade over 17,000 myself. Which I don't consider bad with 3 websites and a fourth in devlopment along with a host of test installations.
|
|
#12
|
||||
|
||||
|
Using quietFinn's Inodes Script for Hostgator (acronymned QFISH
) I found out that my 3 Joomla sites installation and a couple of development sites are using 6,695 inodes. The actual webspace I'm using is only about 1.3GB.Which means, I will be surpassing the 50T inodes limit if I have about 22 subdomains/add on domains all in Joomla and they would only be using less than 10GB of webspace. Even if I have 10MB per inode, that would only be 500,000MB or 500GB of webspaces for the 50T inodes. So, the awesome webspace and bandwidth upgrades is a great marketing strategy to truly "eat up the competition". It's like paying for a bottomless iced tea, knowing that you can only consume about 2 mugs of iced tea. But the price of the 'bottomless' costs about 3 to 4 times the regular glass of iced tea. So you end up paying for the service that you really don't consume. In the case of Hostgator, the clients end up praising Hostgator and eventually spreading the good news and ultimately invite more potential clients to join/register with Hostgator. Which really is not a bad idea, perhaps a great one at that. And I don't think the increase in customer's will bring down the servers, especially when the 50T inodes limit is in effect. Last edited by secure; 10-15-2007 at 01:12 AM. |
|
#13
|
||||
|
||||
|
As was explained further up, this only really applies to you if you're constantly writing and deleting all those files. In your example of 22 Joomla installations, we're really talking about files that are mostly staying the same but databases that are updating. It's unlikely you'd be affected by this limit.
__________________
Follow me on Twitter! http://twitter.com/mrw |
|
#14
|
||||
|
||||
|
secure,
This Inode limit isn't to restrict hard drive space. The limit is there to stop clients from hurting the file system. One example of a possible way of hurting the partition is having a directory with 100,000+ inodes, and constantly deleting / recreating the files. There is a higher chance of you corrupting the directory. When the directory is corrupted, the inodes basically lost on the file system, which would need a file system check to repair it. |
|
#15
|
||||
|
||||
|
Yes, I understand what's the inodes limit is for. It's for preventing corruption of the file system of the servers. Well, exactly as stated above.
For example, I have 4 subdomains. On 1 subdomain i have 10,000 inodes, on 2nd I have 20,000 inodes, on 3rd I have 30,000 inodes and on 4th I have 40,000 inodes. All in all I have a total of 100,000 inodes. But then only 30,000 inodes are active, some being executed, some perhaps being created and deleted. While the rest of the 70,000 are just there on their folders as archives or just backups. Now, that wont really corrupt the directory at all, wouldn't it? On the other hand however, if those 100,000 files that I have are ALL actively being executed, created and deleted, even if those files are just 1MB each. That would really f...k up the server bigtime. Besides, what's the point of having an account with 1TB of webspace if you can only store 50,000 files of 1MB each?
Last edited by secure; 10-15-2007 at 03:48 AM. |
|
#16
|
||||
|
||||
|
Have you been keeping up with the new rulings form the U.S. Appeals Court involving TOS? You really should keep an eye on it because things are changing and I'd hate to see you guys get your a$$ in a jam.
|
|
#17
|
||||
|
||||
|
Could you provide links to these new rulings?
__________________
best regards, George |
|
#18
|
|||
|
|||
|
Im concerned! As a designer im constantaly uploading and deleting stylesheets, images and html files and my usage is a little over 46000 inodes. Should i be worried and should i take my developments sites to a different host?
__________________
|
|
#19
|
|||
|
|||
|
Quote:
Or you could go dedicated |
|
#20
|
|||
|
|||
|
Thanks for that but what consitutes thousands of inodes? Im currently at just over 46000 after ten months with HG.
__________________
|
|
#21
|
|||
|
|||
|
Quote:
index.html = 1inode /bob/ = 1inode /bob/test.html = 1inode |
|
#22
|
|||
|
|||
|
Quote:
__________________
|
|
#23
|
|||
|
|||
|
If you delete files, your inode count goes down
|
|
#24
|
|||
|
|||
|
Kewl, thanks for clearing that up
__________________
|
|
#25
|
||||
|
||||
|
when i am using the following code:
Code:
<?php
print system("find . -printf \"%i\n\" | sort -u | wc -l");
?>
76 76 and when i use the following code: Code:
<?php
system("/usr/bin/quota | /bin/awk '{ if ( $5 ~ /^[0-9]/) total+=$5 } END {print \"Total Inodes :\" , total}'");
?>
Total Inodes : 396 why they are different? and which one is more accurate ? which one i choose? about GatorDaveC: how they appear like this ? what is the code that i have to write in inodes.php? Code:
quota -u davec
Disk quotas for user davec (uid 32388):
Filesystem blocks quota limit grace files quota limit grace
/dev/sda1 4 629145600 629145600 3 0 0
/dev/sda7 84 629145600 629145600 20 0 0
/dev/sda3 8 629145600 629145600 2 0 0
/dev/sda2 0 629145600 629145600 1 0 0
find | wc -l
20
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|