Sync/Copy fails completely if even one file is corrupted or cannot be read.

[ionFish]

Problem: When one or more files is corrupted (and cannot be read either by the OS itself or of course AWS-CLI), the entire sync or cp process fails (fatally) with the following error:

[Error 2] The system cannot find the file specified: u'\\\\server\\path\\to\\file '

Note: I have only tested this on Windows. I tried to delete the files manually, and it returned a "no such file or directory" error.

Not sure how we would fix that, but sync and cp should not fail completely if one file is bad; it should make note of the error(s) and carry on.

[jamesls]

I agree, we should just be displaying an error about the specific file and moving on to the remaining files. We shouldn't be stop the entire sync/cp process.

[ionFish]

@jamesls Unrelated, but I'm curious: why is this written in Python and not C or something?

[ionFish]

@jamesls - This also happens when (for example on a Windows network share) one of the files/directories has permissions set that do not allow read access. This is [Error 5] Access is denied: ...

[blackstar257]

Where does the code live that kills the process when it runs across one of these file system errors?

[jamesls]

In awscli.s3.customization.filegenerator I believe. Note that we are currently working on a fix for this such that any errors that occur when trying to access a file will not stop the entire transfer process. I will update this issue when a fix is available.

[kyleknap]

Closing, issue is fixed via #881 and is merged into the develop branch.