mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #544] Prefix Only Going One Level #310
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#310
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 @herriojr on GitHub (Mar 11, 2017).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/544
I am attempting to use a prefix to mount into a specific folder in S3. It works when I use a top level folder such as /root/ but not when I use /root/subfolder/ even though the folder does exist.
Failed Command
Successful Command
Showing that it does exist
@ErikDahlinghaus commented on GitHub (Mar 29, 2017):
I'm experiencing the same issue.
@RobbKistler commented on GitHub (Mar 29, 2017):
The FUSE stackable module
subdirmight be a workaround@ErikDahlinghaus commented on GitHub (Mar 29, 2017):
Thanks Robb, I haven't tried this yet as goofys is solving my needs for the time being.
@ggtakec commented on GitHub (Apr 2, 2017):
@herriojr
In my test it is working.
I want to know about detail information which is got by dbglevel(as same as -d ption) and curldbg.
(you can see "dbglevel=info,curldbg -f" in my test command)
I think the logs help us to slove this problem.
Thanks in advance for your assistance.
@frankrod commented on GitHub (Sep 20, 2017):
It's working for me in version 1.82 This is how I did it.
s3fs myBucket:/root/firstLvl/ mountFolder/ -o passwd_file=myPasswordFile -o umask=00000@ggtakec commented on GitHub (Mar 30, 2019):
We kept this issue open for a long time.
Is this problem continuing?
We launch new version 1.86, which fixed some problem(bugs).
Please use the latest version.
I will close this, but if the problem persists, please reopen or post a new issue.