mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1429] Segmentation Fault with s3fs 1.87 #756
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#756
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 @adwaitsathe on GitHub (Sep 29, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1429
Additional Information
Running s3fs in docker container. The work load is generated by Cassandra stress tool. Results in segmentation fault. Same problem persisted with 1.86 version.
Mount Command:
Version of s3fs being used (s3fs --version)
Amazon Simple Storage Service File System V1.87
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
root@localhost:/opt/cassandra# apt-cache policy fuse
fuse:
Installed: 2.9.7-1ubuntu1
Candidate: 2.9.7-1ubuntu1
Version table:
*** 2.9.7-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
Kernel information (uname -r)
3.10.0-1062.1.2.el7.x86_64
GNU/Linux Distribution, if applicable (cat /etc/os-release)
root@localhost:/opt/cassandra# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.4 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.4 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
@gaul commented on GitHub (Sep 29, 2020):
Could you try testing with master? #1363 may have fixed this.
@adwaitsathe commented on GitHub (Sep 30, 2020):
The issue seems to have been fixed in master. Could not reproduce it with master.