mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1819] s3fs blocked - most threads hang in AutoLock::AutoLock() -> __lll_lock_wait() #933
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#933
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 @CarstenGrohmann on GitHub (Dec 17, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1819
Dear S3FS Developer,
Running the current master (
5de92e9- "Bump CI to Fedora 35 (#1806)") causes a deadlock.In this setup 4 parallel ZIP processes stores files in a bucket mounted with s3fs. The process got stuck with the following backtrace. The system log doesn't show any information. A separate debug log was not active.
The error occurred just once and I don't have the ability to compile with Clang to use the ThreadSanitizer provide more information
Do you have an idea about the root cause of this issue?
Thank you,
Carsten
Short backtrace;
Full backtrace:
@CarstenGrohmann commented on GitHub (Feb 15, 2022):
All s3fs instances have been running stable for a few weeks. Therefore, I am closing this topic and reopening it with new information if needed.
@gaul commented on GitHub (Jun 12, 2022):
Sorry for the late reply -- you might try ThreadSanitizer deadlock detection next time:
https://github.com/google/sanitizers/wiki/ThreadSanitizerDeadlockDetector
Generally s3fs could use some more stress testing scripts if you want to contribute something!