mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #810] Flaky behavior when fused to sftp directory #467
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#467
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 @dland512 on GitHub (Aug 17, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/810
Additional Information
The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.
Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.79(commit:unknown) with GnuTLS(gcrypt)
Version of fuse being used (pkg-config --modversion fuse)
apparently
pkg-configis not insalltedSystem information (uname -r)
4.4.0-1062-aws
Distro (cat /etc/issue)
Ubuntu 16.04.4 LTS \n \l
s3fs command line used (if applicable)
/etc/fstab entry (if applicable):
s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
Nothing in syslog. Here is the
s3fsoutput. There are a lot of HTTP404s mixed in with some HTTP200s. Keep in mind that this is just a small sample from the logs. There are a ton of entries just like this at the time the file was being transferred.Details about issue
I have sftp set up on an aws ec2 instance with
s3fs. A client in transferring a 20 MB - 30 MB file over via sftp every night directly into the folder that is fused with S3. About half the time the transfer doesn't work and the file never shows up on disk or in S3. I've tried it myself from various clients and I can't reproduce the issue.Is it possible that
s3fsis not playing nicely with sftp? Should I try having them ftp the files to a non-fused directory and then copying it over to the fused directory?@dland512 commented on GitHub (Aug 22, 2018):
FYI, this does seem to be due to some the interaction between sftp and fuse. I have turned off s3fs and am now successfully receiving ftp files. Unfortunately, I can't say exactly what the issue is. Since I don't control the sftp client that is having the issue, I don't have the option of doing a lot of debugging. Some sftp clients work fine and one of them does not.
@gaul commented on GitHub (Feb 2, 2019):
Do you know which operations are failing or blocking? In #928 we discovered that a long-lived write operation will block a simultaneous readdir operation.
@dland512 commented on GitHub (Feb 2, 2019):
Unfortunately, I don't know the specific ftp commands the client was issuing. It seemed like the file was being received then it just disappeared. I would see things like this in the logs:
You can see it uploads a file of 27248920 byes then shortly after that says
sent status No such file. So I think it's possible that this could be caused by #928, unfortunately, I was never able to reproduce the issue on my own. It's something about that specific sftp client combined with the s3fs fuse.@gaul commented on GitHub (Jul 10, 2019):
@dland512
50d13255e4should fix this. Could you test with the latest master and report back?@gaul commented on GitHub (Feb 3, 2020):
Closing due to inactivity. Please reopen if symptoms persist.