You are not logged in.
Strange one this one, my backup that runs on a cron fails with the following error:-
terminate called after throwing an instance of 'Vmacore::SystemException'
what(): No space left on device
I have checked both the main datastore and also the backup datastore and both enough space, if i run the backup manually xsibackup run job001 then it runs fine, but fails on the cron.
You might have reached the maximum number of inodes, check this:
Thanks for coming back with a possible fix, doesn't look like that is the issue.
Any other idea's would be greatly appreciated as running it during the day is a pain
stat -f /
ID: 100000000 Namelen: 127 Type: visorfs
Block size: 4096
Blocks: Total: 467340 Free: 299380 Available: 299380
Inodes: Total: 655360 Free: 648781
That message is coming from ESXi, revise your hardware. Computer systems can fail, but they rarely lie.
Are you saying that it looks like the hardware is failing or is it something else?
Just adding to this, i am backing up to a datastore that is hosted on a NAS which is also being used by another ESXI server, which backs up fine. also the datastore on the ESXI has ample storage space.
So both are fine and i am still seeing this error.
What we are saying is that some ESXi component wrote this to stdout or/and to your log:
'Vmacore::SystemException' what(): No space left on device
This is not an XSIBackup error, some ESXi core component is throwing the message.
You may believe that this is plain nonsense, but we do believe it has something to do with what's actually going on inside your server and we are reminding you that you should delve into the root of that message.
Your ESXi server has multiple volumes serving different purposes, one of them might have no space left. Search for more detailed errors in your /scratch/log directory.