-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ctrl-C does not cleanly unmount #49
Comments
Thanks for the report! It is not clear to me that this is a bug rather than intended behavior. If Ctrl-C is indistinguishable from unmounting the file system (as it was in 2.31 and earlier), you could always just unmount the filesystem rather than pressing Ctrl-C. In 2.32 and newer, Ctrl-C results in the filesystem terminating as quickly as possible without data-loss (assuming that the local cache is kept). Do you have a use case where you depend on Ctrl-C having the same semantics as unmounting? |
Hi, |
Thanks for the additional details! However, it is still not clear to me why you can't trigger a regular unmount before stopping the container, or as part of the container stopping procedure. Having a way to shutdown S3QL as quickly as possible without loosing data is a valuable feature, so I'm really not found of the idea of dropping this in favor of making SIGTERM/SIGHUP an alias for unmount. |
I'm closing this bug report for now. Please feel free to re-open this if you can provide the requested information! |
Version: 2.32 (built from sources in a docker container)
I mount a S3QL FS (I created an authfile2 file meanwhile)
Then CTRL+C and...
It is OK to umount cleanly after mounting without --fg:
It works with version 2.21 (debian stretch package)
CTRL+C
The text was updated successfully, but these errors were encountered: