[GH-ISSUE #731] How to interrupt long lasting operations ? #417

Closed
opened 2026-03-04 01:45:23 +03:00 by kerem · 2 comments
Owner

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):

s3fs#zzz-production /mnt/s3fs fuse _netdev,defaults,noatime,uid=1001,gid=1001,use_cache=/tmp,multireq_max=1000,max_stat_cache_size=100000,allow_other,umask=007,mp_umask=007,iam_role=zzz-production,endpoint=eu-west-1 0 0

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 intr and nointr mount options, but I couldnt find any equivalent for fuse/s3fs...

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): ``` s3fs#zzz-production /mnt/s3fs fuse _netdev,defaults,noatime,uid=1001,gid=1001,use_cache=/tmp,multireq_max=1000,max_stat_cache_size=100000,allow_other,umask=007,mp_umask=007,iam_role=zzz-production,endpoint=eu-west-1 0 0 ``` ### 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 `intr` and `nointr` mount options, but I couldnt find any equivalent for fuse/s3fs...
kerem closed this issue 2026-03-04 01:45:23 +03:00
Author
Owner

@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?

<!-- gh-comment-id:510293545 --> @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?
Author
Owner

@gaul commented on GitHub (Feb 3, 2020):

Closing due to inactivity. Please reopen if symptoms persist.

<!-- gh-comment-id:581294128 --> @gaul commented on GitHub (Feb 3, 2020): Closing due to inactivity. Please reopen if symptoms persist.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#417
No description provided.