Hello Mani,
wow you already have DB2 V10.7
you are on the beta version program?
Just kidding
I think you wanted to say 10.5.7!
That aside, you can simply remove the entry in the ars.cache file for your /cache4 directory, and that's it.
CMOD won't add new files on it, and it will still be able to retrieve the documents back from /cache4 (normally... but you should check in test before doing it in Prod, because you need also to restart CMOD to refresh that information)
the verification of the cache will complain a lot! :-)
I know that CMOD does a LOT of checks on the directory, so maybe it won't be able to retrieve the document in the cache after you remove the entry in ars.cache.... that's why you need to test in your test environment.
The idea behind is that /cache1/retr/ contains all the links to the files in the cache filesystems, so you won't loose anything.
Now why does CMOD write only in /cache4, and not spreading in all the other FS too?
CMOD use a kind of round robin algorithm, that look at the disk space (percentage) available for each cache filesystem.
If he sees that one is nearly empty, then he will prioritize this filesystem, and use only this one, until it reaches the same percentage level of the other cache filesystem.
Maybe a reshuffling of all files in the cache to rebalance the directories would be a good idea... (maybe an improvement request for CMOD Developers
) That reshuffling is today not available, and can be done "manually" if you understand how the cache works. Of course, this needs to be tested before doing anything in production!! :-)
I hope that helps in understanding what happened in your system.