mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #731] How to interrupt long lasting operations ? #417
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#417
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 @gggeek on GitHub (Mar 10, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/731
Version of s3fs being used (s3fs --version)
1.80-2~bpo8+1 - from Debian 8
Version of fuse being used (pkg-config --modversion fuse)
2.9.3-15+deb8u2 - from Debian 8
System information (uname -r)
3.16.0-5-amd64
/etc/fstab entry (if applicable):
Details about issue
Running a 'find' command (by mistake) over a consistent directory tree (60GB of small files) results in a hanging process. The process being in D state, it is not possible to kill it immediately (my understanding is that it will wait for its syscall to terminate).
The question is: is there any way to make the stuck process killable, short of unmouting the whole s3 bucket ?
I know that NFS has/used-to-have
intrandnointrmount options, but I couldnt find any equivalent for fuse/s3fs...@gaul commented on GitHub (Jul 11, 2019):
I tried to reproduce these symptoms with version 1.85 and I was successfully able to ^C a long-running find command. Could you test with the latest version and share more about your environment?
@gaul commented on GitHub (Feb 3, 2020):
Closing due to inactivity. Please reopen if symptoms persist.