Skip to main content
Question

unable to collect log files. There is not enough disk space in the [/opt/commvault/iDataAgent/jobResults/sendLogStagingFolder


Forum|alt.badge.img+5

Hi,

I do partner support and sometimes I advice my customers to collect logs.

I had to notice that under FR36 we currently need to collect Log files manualy often on Linux clients.

sentlogs runs in an error

 

Job Status: [Completed With Error]

The client [ora] got critical error: [There is not enough disk space in the [/opt/commvault/iDataAgent/jobResults/sendLogStagingFolder]. The available free space is [6.00] GB, please make sure to have at least [10.00] GB and retry the operations.].

 

Failed Client(s): ora

 

 

It will take some time until customers find enough space to sadisfy the threshold. May be it make sense to reserve 10GB in the future. May be Setting the Minimum Free Space for the Job Results Directory is not the screw we should turn here.

Do you have a good suggestion what we can do to make “send log files” working again until hundred of Unix machines in an CV environment have increased the “jobresults” size or have been moved ? 

It's annoying to have to repair the tool first before you can tackle the actual issue.

Thanks

Joerg

2 replies

Forum|alt.badge.img+15

Hello ​@Joerg 

Thanks for the great question, here is my understanding of how it works. 

At the start of the log collection job we check to see if we are at any thresholds and if we are not we go ahead with the collection. I do not think this is checked again through out the operation. this means if we set the threshold to low and then a larger log collection runs we could be at risk of causing a disk to get full. If this is shared with the OS then you can cause a server to fall over. 

If your Job Results is on a different disk to your OS you can be a little riskier with the key and tune it aggressively to what you need. 

To be 100% safe, expand the disk.
To get around expanding the disk, reduce the threshold but be aware of the risks. 

Kind regards
Albert Williams

 


Forum|alt.badge.img+5
  • Author
  • Byte
  • 21 replies
  • April 4, 2025

Hello Albert,

Thanks for reply and explanation. My problem lies in the current situation on the ground. Customer did updates from FR28 or FR32 to FR36. In the earlier versions, the thresholds were lower.

In Linux environments, customers planned their machines sparingly. This means that we have an average of 4-6 GB of free space in the file system in which the jobresults folder is located. That is fact.

 

Now he has an issue with his e.g. DB backup. We need log files and we run into the threshhold issue.

 

What should I say to my customer: “with the new faeture release you not only have advantages. Now you need more space that we can collect our logs. Please inform your database users that you will have a downtime because you have to add a new disk or increase the size of the existing disks” (Exaggerated formulation)

 

If possible he move his jobresults folder but that is not the point

.

In the current situation I need logs and may be the content of the jobresults folder itself. I need to tell the customer that he has to collect logs and folder manualy which means more work for the admin. May be the backup admin has to ask the unix admin, may be important informations about the OS needs to be collected in a second step etc. We loose time!

 

It would be better and this is why I opened this question if I can say:” Hey you need to increase your space in the near future but for now you can workaround it <“THIS WAY”> 

“THIS WAY” is a simple command or key or value which I can change with some clicks.

Can you help?

Joerg

 

By the way: Requirements point to

Job Results Directory Disk Space Calculation

Please add that you need a minimum of 10GB (Threshhold) independent from your calculation. 

 

 

 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings