Good evening, I've got a question, in our production system there is an application called Intermediate which ftp service is the core to to send back and forth from/to diferent destinations
Gradually FS / was ruuning out space and we took a long time to figure out what precesses were eating up this FS /
our SA found a folder called /dcs/data13 taking up 5.4 GB of space located 0n FS / (root)
to checku up /dcs/data13 is not a FS but a folder mounted in FS /,
I've got a couple of questions:
1 why i cant see the path when execute the command df -h
2 why the application let me create /dcs/data13 asuming it was a path? it shoud have yield an error if filesytem /dcs/data13 didnt exist
3 is true if FS / get 100 % full is probably the server shut itself down ?
I appreciate your help in advanved, here is the scrren of FS mounted
This will run a while, but will show you a path for each directory, it chops off the list with the 20 largest directories. By largest I mean how much space the directory uses, this includes subdirectories. So with one subdirectory using lots of space each of the parent directories of the biggie will also show up in the list. Hence look for more than just one, I guessed 20, so one of them will likely be the bad guy directory itself.
If you are having problems with processes silently using space, consider implementing quotas on file systems you need to protect. Also, consider NOT having "ordinary applications" access to writable directories on the / FS. Put the directories somewhere else.
---------- Post updated at 08:23 AM ---------- Previous update was at 08:14 AM ----------
A folder mounted on /dcs/data13 is another file system.
The df shows all currently mounted file systems. I suspect that /dcs/data13 is not permanently mounted via fstab, but on-demand via automounter.
Why??? If it were a file system /dcs/data13 would be a mount point no? So it needs to exist for the FS can be mounted, yet if the FS is not mounted then its just a directory and what is stopping you to write in it?...
Thanks for your help, i run those commands with a slight difference but i hat to cancel it since it was taking more than 4 hours and it never finished.
find /dcs/data08 -type d |
while read dname
do
du -s $dname
done | sort -n
Furthermore it was in the top list using the top command
It will still be high on the list of output from top while it is running, but at least it will just be processing the directories located in /dcs/data/08 instead of every directory in the file hierarchy rooted in /dcs/data/08 . And, it will be invoking du once instead of once for each directory in that file hierarchy.