Sunday, May 5, 2024
 Popular · Latest · Hot · Upcoming
0
rated 0 times [  0] [ 0]  / answers: 1 / hits: 2020  / 1 Year ago, mon, march 6, 2023, 11:17:33

I had recently run a script in our college exam on my computer which was specifically for 32bit(i386) but my ubuntu is amd64 , so the script wouldn't run but then I tried accessing the folders in my home folder which gave me permission denied.
So I did a sudo chmod 777 -R /home/username , which gave me permissions to complete the test even though I was put as an exception to take my test without using the script to run successfully.
After all this and another two days later I started facing problems of less space on my drive but I probably should have had plenty of space.
Then it said that I have 1.4 kb space left on the system. I searched for my problem on the net and somewhere I found an answer on askubuntu which I am not able to find again. It said that, what actually happened is that the home directory should have 644 permission rather than 777 and so the files I deleted had their INODES still present along with the new files I added to the directory and hence there is no space left.
I have removed everything from the home directory and when I try to add a file with size less than a kb it still says no space left. Any help or suggestions will be appreciated.



 running df  gives
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 16229452 15634864 0 100% /
udev 1941220 4 1941216 1% /dev
tmpfs 780000 972 779028 1% /run
none 5120 0 5120 0% /run/lock
none 1949996 9732 1940264 1% /run/shm
overflow 1024 668 356 66% /tmp
/dev/sda3 449082364 281834708 167247656 63% /media/Acer
/dev/sdb1 976762524 250648068 726114456 26% /media/HD-PCTU2

df -h

Filesystem Size Used Avail Use% Mounted on
/dev/sda6 16G 15G 0 100% /
udev 1.9G 4.0K 1.9G 1% /dev
tmpfs 762M 972K 761M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1.9G 14M 1.9G 1% /run/shm
overflow 1.0M 668K 356K 66% /tmp
/dev/sda3 429G 269G 160G 63% /media/Acer
/dev/sdb1 932G 240G 693G 26% /media/HD-PCTU2

gparted Image

i.imgur.com/NK0U349.png

More From » permissions

 Answers
0

The problem was caused because of a log file taking up too much space on the disk. The file was found in the HADOOP_LOG_DIR. We can find it in /etc/hadoop/conf/hadoop-env.sh. Here while configuring we setup the HADOOP_LOG_DIR.



I found them using:

find / -size +100M -ls.



Just do an rm -rf /var/log/hadoop/ . If your HADOOP_LOG_DIR points to /var/log/hadoop/ else rm -rf that particular location.


[#26631] Tuesday, March 7, 2023, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
nnaisdio

Total Points: 369
Total Questions: 112
Total Answers: 108

Location: Kenya
Member since Mon, Jun 14, 2021
3 Years ago
;