I have a Linux server ( ubuntu 12.4 ) which serve my web application (20 MB) on apache httpd. a few days ago I upgrade it to 12.10, then copied one folder (30 GB) to www folder. suddenly the server hang and I got the Low Graphics Mode message (My screen card is Intel ). So I removed the huge folder and restarted the computer but still got the same message. when I searched here for solutions and tried some of them I got this message: No Space Left on Device then I typed: df -h, I surprised that the usage is %100 !! here is my partitions table:
Number|Start|End|Size|File System|Name Flags 1|17.4k|20.0MB|20.0MB|fat16|boot 2|20.0MB|489GB|489GB|ext4 3|489GB|500GB|10.6GB|linux-swap(v1)
I can't access the my files anymore!
Is there anyway to save me and my server without a format ?
sudo du -h /var --max-depth=1 4.0K /var/tmp 235M /var/www 444G /var/log .. ..
So, the log is huge!!
and when I try:
sudo apt-get autoclean sudo apt-get autoremove
I got: Error! No space left on device
So, I don't know how to delete log files! I'm kinda stuck!
I did delete the archives logs but nothing changes the largest file is
and when I list its files, I got:
-rw-r----- 1 root adm 758 DEC 30 07:37 access_log.1.gz .. .. .. **-rw-r----- 1 root adm 444G JAN 5 08:09 error_log** -rw-r----- 1 root adm 245 DEC 29 13:17 error_log.1.gz
if I tried:
sudo service cups stop
sudo: unable to write to /var/lib/sudo/username/tty2: No space left on device
So, what's next ?
Something weird happened! When I unplugged the computer then replugged it. it works fine and problem gone!! the /var size is completely normal!
But I'm afraid of facing it again. I think my main problem is because of the partitions:
sudo parted -l Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number|Start|End|Size|File System|Name|Flag 1|17.4K|20.0MB|20.0MB|fat16| |boot 2|20.0MB|489GB|489GB|ext4 3|489GB|500GB|10.6GB|linux-swap(v1)
as you see, the home and root are together and not separated. do I have to create a new partition for home?
Anyone has another idea how to avoid that issue again ?
aaaand the problem is back :( I didn't do anything ! I don't know what caused it!