Lately, I've noticed it's been having troubles transferring certain files, stalling out or timing out, and then leaving the .filepart files there (as would be expected for resume-ability)
However, what's strange about these is that I cannot remove them on the server, I always get permission denied, file in use errors, but the process using them should be long finished or timed out. In cygwin, I can list the file permissions, and I get strange results:
$ ls -l ls: cannot access 201-B Economics.one.filepart: No such file or directory ls: cannot access 371-A Thermo.one.filepart: No such file or directory total 65496 ?????????? ? ? ? ? ? 201-B Economics.one.filepart -rw-rw-rw- 1 Jim None 35886976 Feb 22 10:13 371-A Thermo.one ?????????? ? ? ? ? ? 371-A Thermo.one.filepart -rw-rw-rw- 1 Jim None 10317843 Feb 22 10:13 389-A Electric Machinery.one.filepart
326 (ETerminal) Permission denied. * 2008-02-22 16:11:50.326 Error code: 3 * 2008-02-22 16:11:50.326 Error message from server: Permission denied * 2008-02-22 16:11:50.326 Request code: 3 . 2008-02-22 16:11:50.326 Asking user: . 2008-02-22 16:11:50.326 Cannot create remote file 'myDocuments/OneNote Notebooks/Spring08/201-B Economics.one.filepart'. ("Permission denied. . 2008-02-22 16:11:50.326 Error code: 3 . 2008-02-22 16:11:50.326 Error message from server: Permission denied . 2008-02-22 16:11:50.326 Request code: 3") * 2008-02-22 16:11:50.341 (EScpSkipFile) Cannot create remote file 'myDocuments/OneNote Notebooks/Spring08/201-B Economics.one.filepart'. * 2008-02-22 16:11:50.341 Permission denied. * 2008-02-22 16:11:50.341 Error code: 3 * 2008-02-22 16:11:50.341 Error message from server: Permission denied * 2008-02-22 16:11:50.341 Request code: 3 . 2008-02-22 16:11:50.341 Closing connection.
I've got a hunch that this might've started due to putting my laptop into sleep while the backup script was running, or perhaps it's due to a hidden resume dialog that the script automatically answers no to?
Also, those filepart files with the "?" permissions (I assume that's what cygwin must report when they're in use), they go back to normal after power cycling the windows server. This is a somewhat non-clean failure though, since it leaves the files locked until a reboot.
Any ideas on how to fix this, or prevent it from happening?