mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #655] Unable to mount folder in bucket with capital characters #373
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#373
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @divyenduz on GitHub (Oct 7, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/655
If I try to mount a specific folder from a bucket which contains capital characters on MacOS.
I get no error from
s3fsbut if I click the mount point in Finder, it crashes Finder and doing a CD from terminal yields no result.umount <mountpoint>takes a while but unmounts such a mount.I am using commands like
Here
divyendusinghis the bucket name andSandBoxis a pre-existing directory in this S3 bucket.Please let me know if I can help you replicate/debug this in any manner.
Additional Information
/etc/fstab entry (if applicable):
NA
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
This is the output without using dbglevel, curldbg. I will post the output with debug flag as a separate comment
Details about issue
@divyenduz commented on GitHub (Oct 7, 2017):
I just noticed that this is happening for the name
SandBox. I created another folder namedAppleBananaand it worked.Making the contents of
SandBoxandAppleBananasame and testing again.@divyenduz commented on GitHub (Oct 7, 2017):
Yes, it works even if the content is same in these folders. It only does not work when folder name is
SandBox. Pasting the results of boths3fs -f -d divyendusingh:/AppleBanana ./s3fsands3fs -f -d divyendusingh:/SandBox ./s3fsfor references3fs -f -d divyendusingh:/AppleBanana ./s3fss3fs -f -d divyendusingh:/SandBox ./s3fs@divyenduz commented on GitHub (Oct 7, 2017):
I think this has to do with the regions of the bucket. However, logs show that it tries
us-east-1first and falls back toap-southeast-1for both commands.Investigating further.
@ggtakec commented on GitHub (Oct 8, 2017):
@divyenduz It seems that S3 returns 404 error for /SnadBox, the error is NoSuchKey.
We need to check about this error, and command line for s3fs(and fstab), etc.
Following page about NoSuchkey:
https://forums.aws.amazon.com/message.jspa?messageID=88655
@sqlbot commented on GitHub (Oct 8, 2017):
Probably related to the fact that the S3 console does not require an actual object named
foo/in order to display a folder -- if a file namedfoo/barexists, the console will display a folder even without the placeholder object.But s3fs seems to require the placeholder in this case.
A possible solution to make this work would be to create that dummy object: Cautiously, you could mount the root of the bucket, and
ls -l SandBox. If it shows up in the listing, execute achmodorchownof it. If not,mkdir SandBox. This should not cause any harm to the objects "in" the folder (because in S3, objects are not really "in folders), and should create the dummy object. Unmount, then try to remount as originally desired.@johnjelinek commented on GitHub (Nov 9, 2017):
I mounted the bucket,
chown'd the path I needed, unmounted the bucket, re-mounted with thebucket:/pathand it worked!@gaul commented on GitHub (Feb 3, 2020):
Closing due to inactivity. Please reopen if symptoms persist.