{"action":"opened","issue":{"url":"https://api.github.com/repos/s3fs-fuse/s3fs-fuse/issues/127","labels_url":"https://api.github.com/repos/s3fs-fuse/s3fs-fuse/issues/127/labels{/name}","comments_url":"https://api.github.com/repos/s3fs-fuse/s3fs-fuse/issues/127/comments","events_url":"https://api.github.com/repos/s3fs-fuse/s3fs-fuse/issues/127/events","html_url":"https://github.com/s3fs-fuse/s3fs-fuse/issues/127","id":58479990,"number":127,"title":"Directories/files uploaded from s3cmd sync aren't readable by s3fs if they have parentheses in name","user":{"login":"jsit","id":643417,"avatar_url":"https://avatars.githubusercontent.com/u/643417?v=3","gravatar_id":"","url":"https://api.github.com/users/jsit","html_url":"https://github.com/jsit","followers_url":"https://api.github.com/users/jsit/followers","following_url":"https://api.github.com/users/jsit/following{/other_user}","gists_url":"https://api.github.com/users/jsit/gists{/gist_id}","starred_url":"https://api.github.com/users/jsit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jsit/subscriptions","organizations_url":"https://api.github.com/users/jsit/orgs","repos_url":"https://api.github.com/users/jsit/repos","events_url":"https://api.github.com/users/jsit/events{/privacy}","received_events_url":"https://api.github.com/users/jsit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-21T23:31:47Z","updated_at":"2015-02-21T23:31:47Z","closed_at":null,"body":"I *believe* this is a problem in combination with these two tools, s3cmd and s3fs. I don't know where to file the bug.\r\n\r\n1) If I create a directory in my S3 bucket with parentheses in the name, it shows up just fine in s3fs.\r\n2) 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.\r\n3) Only when I mount a directory created with (2) using s3fs does the directory with parentheses become unreadable on the mounted S3 bucket. "}}