mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #332] s3fs: BUCKET bucket.name.with.dots, name not compatible with virtual-hosted style. #172
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#172
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 @martyychang on GitHub (Jan 13, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/332
When I try to mount a bucket where the bucket name has periods in it (e.g., "bucket.name.with.dots"), the attempt to mount fails with the following error:
I am able to successfully mount other buckets that have simple alphanumeric names (e.g., "bucket1").
@RobbKistler commented on GitHub (Jan 13, 2016):
The alternative to virtual-hosted style requests is path style requests:
@martyychang commented on GitHub (Jan 13, 2016):
Thank you for the quick tip, @RobbKistler ! That worked like a charm.
@RML-Admin commented on GitHub (Apr 1, 2018):
I am running into a problem with buckets with dots in their names.
I can see <mount_dir> in
df -h.But, I don't see anything in
mount_dirwhen Ils <mount_dir>. When Icd <mount_dir>andls, I see the following error message:s3fs version is 1.83
@trajano commented on GitHub (Sep 3, 2019):
Can we have an equivalent in /etc/fstab form?
@ckujau commented on GitHub (Jan 3, 2021):
Apparently s3fs.cpp:4915 only checks that
bucket names cannot contain upper case characters in virtual-hosted style. I.e renaming buckets (if possible) or creating a bucket with a valid name will help here too.@ctrlcctrlv commented on GitHub (Apr 8, 2023):
That "solution" of using the path req style is everywhere but is worse and slower. This should have remained open.