[GH-ISSUE #1325] Random crashes when locally mounting endpoint #710

New issue

Closed

opened 2026-03-04 01:48:06 +03:00 by kerem · 2 comments

kerem commented

2026-03-04 01:48:06 +03:00

Owner

Originally created by @thyvile on GitHub (Jul 6, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1325

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.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

1.85

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

2.9.2

Kernel information (uname -r)

3.10.0-1062.1.2.el7.x86_64

GNU/Linux Distribution, if applicable (cat /etc/os-release)

NAME="Red Hat Enterprise Linux Server"
VERSION="7.7 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.7"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.7 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.7:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.7
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.7"

s3fs command line used, if applicable

s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)

utimens /dev.test.ru/sberprint01/.&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-/tmp 1593176660.353898909 1593176660.353898909
getattr /dev.test.ru/mfu-0001/.&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-/tmp
getattr /dev.test.ru/print01/.&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-/tmp
unique: 91895, success, outsize: 120
unique: 91901, opcode: READDIR (28), nodeid: 40, insize: 80, pid: 540
readdir[0] from 0
unique: 91900, success, outsize: 120
unique: 91902, opcode: READDIR (28), nodeid: 17, insize: 80, pid: 1423
readdir[0] from 0
unique: 91902, success, outsize: 80
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Аварийный останов

Details about issue

We're using s3fs for our Dovecot installation. Unfortunately after some time s3fs shuts down with either std::bad_alloc or std::length_error. The mountpoint then shows d????????? permissions and we're unable to access it. We'll try to use 1.86 but I didn't see any fixes for this kind of error. Any tips?

Originally created by @thyvile on GitHub (Jul 6, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1325 ### 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._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) 1.85 #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) 2.9.2 #### Kernel information (uname -r) 3.10.0-1062.1.2.el7.x86_64 #### GNU/Linux Distribution, if applicable (cat /etc/os-release) NAME="Red Hat Enterprise Linux Server" VERSION="7.7 (Maipo)" ID="rhel" ID_LIKE="fedora" VARIANT="Server" VARIANT_ID="server" VERSION_ID="7.7" PRETTY_NAME="Red Hat Enterprise Linux Server 7.7 (Maipo)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:redhat:enterprise_linux:7.7:GA:server" HOME_URL="https://www.redhat.com/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7" REDHAT_BUGZILLA_PRODUCT_VERSION=7.7 REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux" REDHAT_SUPPORT_PRODUCT_VERSION="7.7" #### s3fs command line used, if applicable #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) utimens /dev.test.ru/sberprint01/.&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-/tmp 1593176660.353898909 1593176660.353898909 getattr /dev.test.ru/mfu-0001/.&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-/tmp getattr /dev.test.ru/print01/.&BB4EQgQ,BEAEMAQyBDsENQQ9BD0ESwQ1-/tmp unique: 91895, success, outsize: 120 unique: 91901, opcode: READDIR (28), nodeid: 40, insize: 80, pid: 540 readdir[0] from 0 unique: 91900, success, outsize: 120 unique: 91902, opcode: READDIR (28), nodeid: 17, insize: 80, pid: 1423 readdir[0] from 0 unique: 91902, success, outsize: 80 terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Аварийный останов ### Details about issue We're using s3fs for our Dovecot installation. Unfortunately after some time s3fs shuts down with either std::bad_alloc or std::length_error. The mountpoint then shows d????????? permissions and we're unable to access it. We'll try to use 1.86 but I didn't see any fixes for this kind of error. Any tips?

kerem

2026-03-04 01:48:06 +03:00

closed this issue
added the
need info
label

kerem commented

2026-03-04 01:48:07 +03:00

Author

Owner

@gaul commented on GitHub (Jul 7, 2020):

Could you test again with master? This includes a parsing fix 97c249d5b9. If symptoms persist, please attach gdb and get a backtrace.

@gaul commented on GitHub (Jul 7, 2020): Could you test again with master? This includes a parsing fix 97c249d5b922989e5a191346ab40737baaecd5de. If symptoms persist, please attach `gdb` and get a backtrace.

kerem commented

2026-03-04 01:48:07 +03:00

Author

Owner

@gaul commented on GitHub (Aug 1, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

@gaul commented on GitHub (Aug 1, 2020): Closing due to inactivity. Please reopen if symptoms persist.

kerem referenced this issue

2026-03-04 02:01:19 +03:00

[PR #710] [MERGED] add disk space reservation #1614