is there any known reason which could lead to an excessive growth of NMSROOT/conf/csdiscovery/DiscoveryStatusObj?
I know that the file holds all information of the last (or current) discovery job. But in a network with around 100 devices I've got the feeling 7GB is a huge amount of data;
As well this did happen only for one discovery cycle which finally leads to other failed processes because the system was running out of diskspace. To recover the system, I stopped and restarted dmgtd and deleted the file; The subsequent discovery processes did run without a problem as before.
Is there a possibility to troubleshoot the cause of this behaviour and to prevent the system from killing itself (by eating up the whole diskspace)?
No. The problem has been reported about 18 other times. In every case, the file was simply deleted, and a new Discovery was run. It rarely comes back.