Case-sensitive S3 folders versus Windows non case-sensitive
Thanks for the feedback. That's what my thinking was, too: to migrate to "one" folder. This occurred because at first there were manual file moves being done and S3 keys were created manually as well, with different case then Windows folder names; however, we automated some of this using AWS CLI, which was using the Windows folder names exactly and resulted in the "duplicate" folders on S3.
So when I unmount and remount, it will fix the mappings from local Windows drive to S3? How long does mounting take?