Interrupted downloadDir() fails to resume

[aaroncowie]

Steps to reproduce:

1. call downloadDir on a large bucket with lots of nested folders
2. Interrupt script halfway (ctrl-c)
3. Re-run script

You will receive various filesystem errors, seemingly on the files that were being touched when the process was ended.

Examples:
Error: EISDIR: illegal operation on a directory, open
Error: EPERM: operation not permitted, unlink
Error: ENOENT: no such file or directory, open

This happens every time, it is not intermittent.

Is there any way I can work around this? I don't mind if the sync takes forever, I'm more concerned that it doesn't get stuck in an invalid state.

[jasiedu]

Having the same issue.
unable to download: Error: EISDIR, open...

[alexisreina]

Same issue here... I updated graceful-fs dependency to version 4 and seems to work so far. I'm downloading 3 prefixes? from a bucket... over 7.500 files and 250 folders. There's an open issue #122 to upgrade graceful-fs from version 3 to 4, as monkey-patching is no longer supported.

I opened my node_modules folder, find the s3 module package.json and update the graceful-fs dependency to the 4.1.4.

run npm update inside the s3 folder.

[celicoo]

Not working here. I've already try to update graceful-fs.

[celicoo]

Any updates on this subject?

[cstjohn-bhg]

Bump, this error interrupts downloadDir() at about 1/4 progress consistently for me.