Error: S3 error: No space left on device.

[HansMeiser]

Hello,

i do some tests with an S3 Repo on a NetApp.
In Veeam i have a scale-out repo which is based on a 10T performance and a 20T capacity backup repo.

I created a job which stores some VMs daily to this S3 Sobr. this was running fore some weeks without problems.
Since a few days i get an errormessage, but only 3 of the VMs are affected. May job fails with: Error: S3 error: No space left on device.
This is suprising, I can see that performance repo is used 3,5T and capacity 325G, so there should be enough space left. And why should the repo have no empty space only for 3 VMs, others are stored the normal way.
In between the standard job "scale-out S3 offload" also fails, but this was fixed by a rescan of the Sobr.
I deleted these 3 VMs from backup, this also fails with message "no space left on device", but its not visiblke any more.
My backupjob still fails and iam running out of ideas now.

Please give me a hint, what should i check next?

Thanks,
Hans

[Mildur]

Hi Hans,

Unfortunately, this isn’t something we can investigate through a forum post.
Please comply with our forum rules and discuss technical issues, especially environmental ones with Customer Support first before bringing them to the forum.
After you’ve created the case, please share the case number with us here.

S3 error: No space left on device.

I assume it might be related to free disk space on volume with the temp folder on the gateway server — the one handling offloads from the Performance Tier to the Capacity Tier.
Our Support team can confirm the exact root cause by reviewing the log files.

Thank you,
Fabian