mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #115] Connection keeps dropping with multi-level directories #70
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#70
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 @movence on GitHub (Jan 28, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/115
mounting a bucket using IAM written to /etc/passwd-s3fs
s3fs -d -f -o allow_other,use_cache=/tmp,retries=5,rw,multireq_max=7 test_bucket /mnt/s3tried both with and without '-d -f' and got the similar problems
The leaf files are in usually 3 or 4 deep down in directory hierarchy.
reading files under /mnt/s3 is fine, but the connection gets lost even doing ls -l on sub3 level. It looks like the behavior is more random as going into sub directories.
@movence commented on GitHub (Feb 4, 2015):
OK, deleting all existing directories helped it working normally. Creating multi-level directory hierarchy after starting from a scratch works fine.
Another issue that I am running into is that I have built the directory hierarchy on machine A, then mounted the same bucket on machine B. Machine B CANNOT even 'ls -l' on any of directories created by machine A through s3fs. I'm using s3fs on both machines, but B fails to read what A has created.
There is no issue reading files or directories created by machine B from A.
It does not look like this repository is "very" active, so I am just posting this while keeping my fingers crossed with NFS using EBS on EC2.
@gaul commented on GitHub (Feb 4, 2015):
@movence s3fs is not well-suited for sharing files between multiple clients; it lacks the consistency and leasing protocols that NFS and CIFS provide. You might improve your experience by tuning the various cache and timeout values, e.g.,
stat_cache_expire. s3mper and YAS3FS might provide stronger guarantees via using some external storage.@movence commented on GitHub (Feb 7, 2015):
@andrewgaul thanks! It looks like NFS does the job I was looking for.
@ggtakec commented on GitHub (Jan 17, 2016):
I'm closing this issue, if you have a problem yet, please post new issue or reopen this issue.
Thanks in advance for your help.