mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #759] Segmentation Fault #438
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#438
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 @everskies on GitHub (May 12, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/759
Version of s3fs being used (s3fs --version)
1.83
Version of fuse being used (pkg-config --modversion fuse)
2.9.4
System information (uname -r)
4.4.0-112-generic
Distro (cat /etc/issue)
Ubuntu 16.04
s3fs command line used (if applicable)
s3fs storage /home/s3 -f -d -o passwd_file=~/.passwd-s3fs -o url=https://url/ -o use_path_request_style -o nonempty -o allow_others3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs)
dmesg:
Details about issue
I'm getting random SegFaults while transfering (uploading) files using rsync encrypted by gocryptfs. this usually happens after a couple hours / days and I'm unsure why.
The S3 backend is a S3 compatible Ceph cluster.
Any ideas?
@gaul commented on GitHub (Jan 24, 2019):
Can you try running s3fs under Valgrind which may reveal the source of these symptoms?
@gaul commented on GitHub (Mar 15, 2019):
Could you test again with 1.85 which includes
f53503438c?@gaul commented on GitHub (Apr 9, 2019):
Closing due to inactivity. Please reopen if symptoms persist.