Timeline for Can rsync ignore errors that happen due to NFS cache inconsistency?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 16 at 4:31 | comment | added | Gordon Davisson |
Is it possible to have rsync connect to the server directly, rather than over NFS (i.e. use rsync ... servername:/server/path rather than rsync ... /mnt/mountpath)? rsync is really designed to handle the remote access itself (usually over ssh), and tends to perform better that way. And it should avoid this problem, at least if you can have both rsync processes work this way.
|
|
| Feb 15 at 23:07 | comment | added | Chris Davies | Rather than having two independent processes could you lock-step them? | |
| Feb 15 at 21:37 | comment | added | Kamil Maciorowski |
"I could just wrap it with || true but I'm worried I'd miss other important errors" – A way not to miss some other errors is to convert only exit value 23 to 0: (rsync …; e="$?"; [ "$e" -eq 23 ] && exit 0; exit "$e"). Not perfect, but better than just || true.
|
|
| Feb 15 at 20:33 | history | asked | Kerrick Staley | CC BY-SA 4.0 |