Replies: 6 comments
-
|
Dear Wayne, I updated to the latest version and tried it again tonight. Today I got the same error. I cannot detect the root cause of the error 23 because I cannot find any errors in the messages. Please can you give me an advice why rsync is reporting error 23. Here is the command:
And this is the result: Best regards Rainer |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I looked through the source the other day and didn't see any areas where an error-23 would be signaled without also generating an error message (though I suppose I could have missed something). I'd suggest turning off all the extraneous output ( |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hey Wayne, thank you for your response and checking the code. You are right. I'm using a .NET application which makes SSH commands to the ESX Server. I saw that there was an Error-Property which I can use if the Exit-Code is <> 0. I changed my code and I think tonight I will get an error message during the backup - at the moment I get it every day. I will give you a feedback tomorrow when the error occurs again. Thank you! Best regards Rainer |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hey Wayne, today I got an error message :) . I leave the debug infos (only for testing) all in the command. The problem seems to be that one file could not be renamed. But: renaming the file was done successfully. See here: My command:
Error: But renaming was successfully done! I checked it here: Do you have an idea why rsync is reporting that rename was not executed successfully? The backup storage "storage01 (VOL_1_ESX_BACKUP)" is a QNAP Enterprise Storage attached as NFS-3 (tried NFS-4 with the same results) with a ext4-Filesystem. Addional info of the command result (without the error): Best regards Rainer |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hey Wayne, do you have an idea why this happens on renaming a file (although the file was renamed successfully). I got the behaviour every day. Maybe there exists a (debug) option which I can test. Best regards Rainer |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Rsync just reports the errors from your OS. You'll need to figure out what's going on with the OS. Judging from the paths, it might be some weird NFS locking behavior or something like that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear all,
we are using an ESX 6.7 Host and attached two QNAP Shared Storages to the host via Fiber 10GBit/sec. One storage for productive VMs - the other only for VM backup via rsync (pretty old version 3.1.0).
We are backup every week all VMs which are not running! The productive VMs storage is attached bia NFS 3 - the backup storage via NFS 4.1.
Now the problem is: We are backup hundreds of VMs and sometime I get an error 23. I double checked the switches, cables and our monitor software and it looks like this is not a hardware error. I checked the file systems and there are ok.
We get these errors since we changed our volume type of our Backup-Storage from VMFS to NFS. Previously we backuped from NFS 3.1 to VMFS (on the same storage).
I executed the following command and got the results:
/tmp/rsync -aSWvv --info=backup,copy,del,flist2,misc2,mount,name1,name2,remove,skip,stats3,symsafe --debug=all "/vmfs/volumes/storage03 (VOL_1_ESX)/Test DEV - PACK.backup/" "/vmfs/volumes/storage01 (VOL_1_ESX_BACKUP)/Backup/Test DEV - PACK"Result:
After this i executed the rsync command again and there was no error:
It look like the first backup (with the error 23) was successfully! I tried several things e.g. last weeks and started up serveral VMs with the error 23 - everything is working.
Does anybody have an idea whats the reason for this error 23 or is this a bug?
Best regards
Rainer
Beta Was this translation helpful? Give feedback.
All reactions