[GH-ISSUE #127] Directories/files uploaded from s3cmd sync aren't readable by s3fs if they have parentheses in name #80

New issue

Closed

opened 2026-03-04 01:41:50 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:41:50 +03:00

Owner

Originally created by @jsit on GitHub (Feb 21, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/127

I believe this is a problem in combination with these two tools, s3cmd and s3fs. I don't know where to file the bug.

If I create a directory in my S3 bucket with parentheses in the name, it shows up just fine in s3fs.
If I create a local directory with parentheses in the name, then s3cmd sync to my S3 bucket, it shows up just fine in the S3 web interface.
Only when I mount a directory created with (2) using s3fs does the directory with parentheses become unreadable on the mounted S3 bucket.

Originally created by @jsit on GitHub (Feb 21, 2015). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/127 I _believe_ this is a problem in combination with these two tools, s3cmd and s3fs. I don't know where to file the bug. 1) If I create a directory in my S3 bucket with parentheses in the name, it shows up just fine in s3fs. 2) If I create a local directory with parentheses in the name, then `s3cmd sync` to my S3 bucket, it shows up just fine in the S3 web interface. 3) Only when I mount a directory created with (2) using s3fs does the directory with parentheses become unreadable on the mounted S3 bucket.

kerem closed this issue

2026-03-04 01:41:50 +03:00

kerem commented

2026-03-04 01:41:51 +03:00

Author

Owner

@jsit commented on GitHub (Feb 21, 2015):

Apologies -- Please excuse this issue; after some further testing it seems like it's not a matter of parentheses at all. Still diagnosing.

@jsit commented on GitHub (Feb 21, 2015): Apologies -- Please excuse this issue; after some further testing it seems like it's not a matter of parentheses at all. Still diagnosing.

kerem commented

2026-03-04 01:41:51 +03:00

Author

Owner

@Ishotihadus commented on GitHub (May 4, 2023):

Same here. Have you already solved this problem?

@Ishotihadus commented on GitHub (May 4, 2023): Same here. Have you already solved this problem?

kerem commented

2026-03-04 01:41:51 +03:00

Author

Owner

@Ishotihadus commented on GitHub (May 4, 2023):

I found that this problem occurs when the sigv2 option is enabled. Turn off the option to solve this problem.

@Ishotihadus commented on GitHub (May 4, 2023): I found that this problem occurs when the sigv2 option is enabled. Turn off the option to solve this problem.