Open pako-pl opened 6 years ago
@pako-pl Can you clarify what the expected behavior would be for this scenario? Would it be to?
item.208
from S3item.208
and replace it with the object item.208
from S3I think it would be the latter, but it may not be possible to do because the commands are trying to map a key/value store to a file system which has caused other issues like this in the past.
The expected behavior would be to delete the item.208
directory from the target and replace it with the item.208
object from S3, as I am running a "sync" with the "--delete" flag.
I think I have the same issue here. Any progression? Workaround?
same issue here
This issue happens also when you try to sync a s3 bucket that has equally named files and directories under the same hierarchy level. I assume this happens because the s3 sync download's first the equally named folder locally and then fails when it download's the equally named file.
Can be easily reproduced:
item.208 is a file in the source S3 bucket and a directory in the target local directory. The situation occured after we moved around some files in S3, including replacing a directory with a file with the same name. It caused our backups to stop running due to "[Errno 21] Is a directory". We would expect "s3 sync" with the "--delete" flag to be able to cope with such a situation.