Disk Space Filling Up Fast?


#1

I could be mistaken, as I look at way too many df -h screens over the course of any given week, but it seems like it was a fraction of this, last I checked, less than a week ago. Is there a problem with some accounts turning on unnecessary insane-o logging or something? Could it be other customer-initiated (intentional or otherwise) abuse? Unfortunately, the odds are also pretty high that there are DH competitors unscrupulous enough to set up accounts and then try to do stuff to break things. Anyway, when disk usage gets this high, performance definitely starts taking a hit. Thanks for all the hard work trying to keep the dream of hosting alive!

bart:~>df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda1 2.0G 1.4G 551M 72% /
/dev/hda3 6.9G 4.8G 1.8G 74% /usr/local
10.3.19.68:/vol/boot/postal/dhs 56G -8.0Z 186G 101% /home/.dhs
10.3.100.105:/vol/boot/postal/fuzznut .1T 1002G 106G 91% /home/.fuzznut
10.3.100.104:/vol/boot/postal/jinsen .1T 1002G 106G 91% /home/.jinsen
10.3.100.105:/vol/boot/postal/jocasta .1T 1002G 106G 91% /home/.jocasta
10.3.100.104:/vol/boot/postal/jockey .1T 1002G 106G 91% /home/.jockey
10.3.100.105:/vol/boot/postal/johannesburg .1T 1002G 106G 91% /home/.johannesburg
10.3.100.104:/vol/boot/postal/keerokee .1T 1002G 106G 91% /home/.keerokee
10.3.100.104:/vol/boot/postal/keets .1T 1002G 106G 91% /home/.keets
10.3.100.105:/vol/boot/postal/kekkonen .1T 1002G 106G 91% /home/.kekkonen
10.3.100.104:/vol/boot/postal/leland .1T 1002G 106G 91% /home/.leland
10.3.100.105:/vol/boot/postal/lemming .1T 1002G 106G 91% /home/.lemming
10.3.100.104:/vol/boot/postal/mallymal .1T 1002G 106G 91% /home/.mallymal
10.3.100.105:/vol/boot/postal/malted .1T 1002G 106G 91% /home/.malted
10.3.100.104:/vol/boot/postal/ness .1T 1002G 106G 91% /home/.ness
10.3.100.105:/vol/boot/postal/nessu .1T 1002G 106G 91% /home/.nessu
10.3.100.104:/vol/boot/postal/opium .1T 1002G 106G 91% /home/.opium
10.3.100.104:/vol/boot/postal/oprah .1T 1002G 106G 91% /home/.oprah
10.3.100.104:/vol/boot/postal/patch .1T 1002G 106G 91% /home/.patch
10.3.100.104:/vol/boot/postal/patchouli .1T 1002G 106G 91% /home/.patchouli
10.3.19.117:/vol/boot/postal.localbackups/bart .1T 995G 57G 95% /mnt/filerbackup
10.3.19.117:/vol/boot/postal.crontabs/bart .1T 995G 57G 95% /usr/local/var/spool/cron/crontabs


#2

I’m surprised I could still add content to my site.

Yes, I have an opinion.

Get a minimum 50% off with the “haveadreamyday” promo code, and… have a dreamy day. Original, no?


#3

If you see 101% it just means the volume is larger then the machine has a counter for. If you see 100% on the other hand, PANIC! That should never happen though as we are always adding more drive capacity to the system. 20 more TBs are arriving on monday for instance.


#4

Ah… I think I get the idea now. So in this case, the machine only keeps track of about 56 GB, then? Or have I gone and not understood what you were saying?

Yes, I have an opinion.

Get a minimum 50% off with the “haveadreamyday” promo code, and… have a dreamy day. Original, no?


#5

Close, but more exactly the machine might have a counter of X bits and the couter can only store numbers up to a certain size and if you go beyond that you end up with jibberish in the size column. Df then sees the nonsensical 56GB size and 200 GB used and gets 101% as the percentage used.


#6

Ah, now I see… this explains why most if not all the filers df brings up either appear nearly full, or overfull.

Yes, I have an opinion.

Get a minimum 50% off with the “haveadreamyday” promo code, and… have a dreamy day. Original, no?


#7

Good news on the incoming TB’s. Comments on df are quite true. There’s also the inode picture, of course, which is often helpful. Dream on!

art:~> df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hda1 263296 104635 158661 40% /
/dev/hda3 919296 56889 862407 7% /usr/local
10.3.19.68:/vol/boot/postal/dhs 55876659 49410336 6466323 89% /home/.dhs
10.3.100.105:/vol/boot/postal/fuzznut 75999984 66678953 9321031 88% /home/.fuzznut
10.3.100.104:/vol/boot/postal/jinsen 75999984 66678953 9321031 88% /home/.jinsen
10.3.100.105:/vol/boot/postal/jocasta 75999984 66678953 9321031 88% /home/.jocasta
10.3.100.104:/vol/boot/postal/jockey 75999984 66678953 9321031 88% /home/.jockey
10.3.100.105:/vol/boot/postal/johannesburg 75999984 66678953 9321031 88% /home/.johannesburg
10.3.100.104:/vol/boot/postal/keerokee 75999984 66678953 9321031 88% /home/.keerokee
10.3.100.104:/vol/boot/postal/keets 75999984 66678953 9321031 88% /home/.keets
10.3.100.105:/vol/boot/postal/kekkonen 75999984 66678953 9321031 88% /home/.kekkonen
10.3.100.104:/vol/boot/postal/leland 75999984 66678953 9321031 88% /home/.leland
10.3.100.105:/vol/boot/postal/lemming 75999984 66678953 9321031 88% /home/.lemming
10.3.100.104:/vol/boot/postal/mallymal 75999984 66678953 9321031 88% /home/.mallymal
10.3.100.105:/vol/boot/postal/malted 75999984 66678953 9321031 88% /home/.malted
10.3.100.104:/vol/boot/postal/ness 75999984 66678954 9321030 88% /home/.ness
10.3.100.105:/vol/boot/postal/nessu 75999984 66678954 9321030 88% /home/.nessu
10.3.100.104:/vol/boot/postal/opium 75999984 66678954 9321030 88% /home/.opium
10.3.100.104:/vol/boot/postal/oprah 75999984 66678954 9321030 88% /home/.oprah
10.3.100.104:/vol/boot/postal/patch 75999984 66678954 9321030 88% /home/.patch
10.3.100.104:/vol/boot/postal/patchouli 75999984 66678954 9321030 88% /home/.patchouli
10.3.19.117:/vol/boot/postal.localbackups/bart 31876680 23167975 8708705 73% /mnt/filerbackup
10.3.19.117:/vol/boot/postal.crontabs/bart 31876680 23167975 8708705 73% /usr/local/var/spool/cron/crontabs