`s5cmd cp` fails with chmod operation not permitted

[yellowtailfan]

When I use s5cmd version 2.3.0 to copy from S3 to local:

s5cmd cp <s3 path> <local path>

on WSL2 and where the local path does not allow metadata writes on files then I get this error:

ERROR "cp <s3 path>": chmod <local path>: operation not permitted

s5cmd does not create the copied file and leaves behind an empty file named <original filename><hash>.

It would be nice to have an s5cmd flag like --no-preserve that disables metadata write operations like chmod or file modification times. This would be the like an inverse of the proposal in #350.

In my case the local path is a Google Drive synced folder running on Windows, but I am running s5cmd from WSL2 with the Google Drive mounted using:

H: /mnt/h drvfs defaults 0 0

A work around is to copy to a native Linux filesystem under WSL2 first, then do a second copy into the Google Drive.

Another work around might be to adjust the mount options for the Google Drive to allow chmod operations.