| 8:43 pm on Oct 25, 2003 (gmt 0)|
Normal files that you can not delete and is not from you is not added to your disk quota.
A other reason can be that the files that you have on your windows system is 23.2 Mb, but if you have a unix/linux webserver than files take more space. Special when you have a lott of (small) files, space can easly be doubled.
| 8:51 pm on Oct 25, 2003 (gmt 0)|
I have 1.272 files. Is there a formula for calculating the necessary disk space?
| 9:05 pm on Oct 25, 2003 (gmt 0)|
Are you using the same server for email that might figure into it.
| 10:06 pm on Oct 25, 2003 (gmt 0)|
Why don't you just ask your host what has taken up the disk space? I suspect you already found the answer with those three files. It's quite common to have stats and logs count against total quota.
| 10:24 pm on Oct 25, 2003 (gmt 0)|
> Are you using the same server for email that might figure into it.
No, I don't have any email.
> Why don't you just ask your host what has taken up the disk space? I suspect you already found the answer with those three files. It's quite common to have stats and logs count against total quota.
Actually I am in the process of communicating with my host. By they are a bit slow - and I feel like I have to find the reasons myself in order to speed up the process.
So stats and logs count? But how about "web.cache"?
| 11:06 pm on Oct 25, 2003 (gmt 0)|
I think web.cache.new and web.cache are used to create your stats. Your host can probably delete those two files. It'll take longer to process the stats though. If these files are being counted, I recommend you try convincing them not to do so first.
I've never seen my files take up double space going from a Windows PC to an *nix server. They pretty much use the same disk amount. I think the problem is elsewhere. Email is a good one too, but you ruled that out. How much of your files can you upload before hitting disk quota? With what you posted so far you're only at 39.2 Megs, try looking around in your account for some other big files like logs.
| 1:42 am on Oct 26, 2003 (gmt 0)|
Like Monus said
|lott of (small) files, space can easly be doubled. |
I have 43 files on the server, 2,395 bytes in Dos
but 184,320 on the server, 'du -s -b'.
43 files + 2 dirs, '.' and '..' = 45 files.
45 *4096 = 184,320.
try in Dos
43 file(s) 2,395 bytes
2 dir(s) 176,128 Allocated
| 2:26 am on Oct 26, 2003 (gmt 0)|
You can probably delete those files safely, I've done so myself. However, it may affect your stats programs, but it may not. You might also be interested in shopping around for a better host that offers more space and faster support. Sticky Me if you want a suggestion.
| 6:30 am on Oct 26, 2003 (gmt 0)|
I agree a directory is 4KB but each file does not balloon up from ~55 bytes to 4KB. On my server, they stay the same size even at the tiny amount per file used in your example. If a file has spaces, it's actually smaller on Linux. The . and .. show -0- bytes.
Since he said how many files and the total amount, go ahead and try to calculate how much you think his files will bloat up. Perhaps he'll say how many directories so you can add in that amount too.
| 6:33 am on Oct 26, 2003 (gmt 0)|
No, it's not a normal practice. Most hosts don't count these files towards the users accounts. Those who do, set permissions on stats folder properly, so users can delete these files themselves. But small percentage of hosts don't do any of these 2 things, and that's pretty bad! Not only you cannot upload files, but if you have any cgi script that writes into a file, all information in this output file will be erased as soon as somebody tries to use your script while there is "disk quota exceed". The file will become corrupt. So if you have one, check it!
That was a main reason why I switched 2 hosts recently. And while searching for the host lately I put this as a special demand: not to count logs or permit me to delete these files.
Another pretty nasty reason is that there may be no space on server left! Your site itself may not take much space, but if their servers are full, you'll still have "disk quota exceed" message. And there is nothing you can do! In this case, run away from such host as far as you can!
| 11:47 am on Oct 26, 2003 (gmt 0)|
Thanks to everybody for their great (although conflicting :) ) advice. The ultimate solution is, of course, to get a new host, but one never knows what "quirks" this new host might have :) . Thatís why I asked about "normal practice".
> With what you posted so far you're only at 39.2 Megs, try looking around in your account for some other big files like logs.
There are lots of other statistics files. I didnít mention the web-log, because thatís the one system-file I would like to keep :)
> Perhaps he'll say how many directories so you can add in that amount too.
I donít have any directories. But the host has placed a few. Iím not sure how many directories are real and how many are aliasís (which also makes adding the size of all the files impossible).
> try in Dos: dir /V
Thereís no V-parameter in my DOS Ė only W. Did you mean to execute this command on my own PC - or on the host?
> Not only you cannot upload files, but if you have any cgi script that writes into a file, all information in this output file will be erased as soon as somebody tries to use your script while there is "disk quota exceed".
You describe the situation perfectly. Whenever somebody writes my guestbook, the whole guestbook is erased! And I canít restore the guestbook, because my disk quota is exceeded! And I canít alter the script to avoid this situation, because my disk quota is exceeded! And I canít put up a warning on my homepage, because my disk quota is exceeded! Aargh!
| 12:40 pm on Oct 26, 2003 (gmt 0)|
|I'm paying for 50 Mb and my site is only 23.2 Mb |
That is a miserably low amount of disk space. Don't know how much you are paying, but reasonably priced accounts with 1GB of disk space are pretty easy to come by.
|Actually I am in the process of communicating with my host. By they are a bit slow |
Definitely sounds like time to move ...
|The ultimate solution is, of course, to get a new host, but one never knows what "quirks" this new host might have |
Just set up a test account with the new hosting company and have a play first. If you can't find a free trial, this will cost very little.
| 2:03 pm on Oct 26, 2003 (gmt 0)|
I'm on Win98 using the 'MS-DOS Prompt'
Also my site is a 'personal website' on Redhat
with a 10 meg limit.
If you are on a Linux box you might try:
'du -s -b /your_dir_space'
Should be about the same as the /V in Dos.
| 9:09 pm on Oct 26, 2003 (gmt 0)|
I still don't get it. Am I supposed to fire the DIR command against my host? Maybe with the FTP QUOTE?
| 11:32 pm on Oct 26, 2003 (gmt 0)|
Those are definitely logs taking up all your space. If they've never been cleaned, they could grow huge, specially raw server logs! The only solution is to wait until your host cleans them. But my advice is that you search for another host, because there is no guarantee this will not happen again. OK, this time they will clean them up, but a month later you'll face the same problem. I've learnt that the hard way.
Before signing up with a new host you can always ask what's their policy about those logs files: do they count towards your space, do they allow users to clean them, etc... That's important. You don't want your account to look like my father-in-law's garage: filled up to the ceiling with his old junk and the car is parked on the driveway. LOL
| 10:37 am on Oct 27, 2003 (gmt 0)|
I had this problem a while ago. I had 100MB of space. I was suprised when I recieved a message saying I had run out of space as I knew I wasn't taking up all the 100MB. So I deleted a few large files and tried to upload some smaller files - but still I got the message!
As others have said, it was all my web stats and logs eating into my space. I tried to delete them but I couldn't and I couldn't upload any more files. I communicated with my host a number of times and explained that it was not right that the stats should eat into my space. They explained that they had problems with the way the logs were stored was a short time and they would fix the problem. Shortly afterward the problem was fixed.
While you might expect this to happen for a free host, if you are paying for space this is unacceptable behaviour. Either complain at them (it could be a problem they are experiencing), or if thats the way it is, change to another host.