Hi Team,
After some weeks on normal behaviour of the system (OMV5), I found that my main USB OS storage was at 90% of 32Gb.
I checked the forum and other sources, and I found (in my case) what was the guilty.
1st we need to know what folder is who has all this data:
Via SSH:
Command:
# sudo du -sh /root/*
Answer:
15G /root/app
4,0K /root/docker-compose.yml
76K /root/openmediavault-omvextrasorg_latest_all5.deb
96K /root/proxy
We see that Something inside folder /root/app does that this folder uses 15Gb, then, we need to be more accurate in our research, and can ask the same command inde the different folders as:
Command:
# sudo du -sh /root/app/*
Answer:
104K /root/app/config
2,1M /root/app/custom_apps
15G /root/app/data
80K /root/app/themes
And, we will do the same for the next folder level:
Command:
# sudo du -sh /root/app/data/*
Answer:
2,8G /root/app/data/appdata_oc6XX0sorXXX
4,0K /root/app/data/Kli
224K /root/app/data/files_external
3,3G /root/app/data/iberGnl
0 /root/app/data/index.html
533M /root/app/data/mwnl
7,5G /root/app/data/nextcloud.log
638M /root/app/data/nextcloud.log.1
As I don't know what is the blue one, I will don't touch it, but, the red line, talks about a LOG file of Nextcloud (running under Portainer via Stacks), and a LOG file, is something that we can sacrifice...
Then, I tried with this command to delete the big file:
Command: rm /root/app/data/nextcloud.log
But, and error was returned:
rm: is not possible to delete '/root/app/data/nextcloud.log': It doesn't exist as file or folder
Then, I tried with the other logfile. .log.1
Command: rm /root/app/data/nextcloud.log.1
And then, when I asked for the folder information again:
Command:
# sudo du -sh /root/app/data/*
Answer:
2,8G /root/app/data/appdata_oc6XX0sorXXX
4,0K /root/app/data/Kli
224K /root/app/data/files_external
3,3G /root/app/data/iberGnl
0 /root/app/data/index.html
533M /root/app/data/mwnl
16K /root/app/data/nextcloud.log
Now, only one LOG file is present, and we rescued a lot of space.
Sure that I something that is not well configured in my NexClould, but maybe it can be useful for other situation where you have this type of issue.
regards!
Hope it will be helpful.