You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest release of fuse-overlayfs (1.13-dev) prints out an annoying warning:
# fuse-overlayfs --version
unknown argument ignored: lazytime
fuse-overlayfs: version 1.13-dev
FUSE library version 3.10.5
using FUSE kernel interface version 7.31
fusermount3 version: 3.16.2
It seems hard coded somewhere, and should probably be removed, or at least be provisioned only after it has been validated to be compatible with the library/other APIs.
# fuse-overlayfs -h
unknown argument ignored: lazytime
usage: fuse-overlayfs [options] <mountpoint>
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: 10)
-o allow_other allow access by all users
-o allow_root allow access by root
-o auto_unmount auto unmount on process termination
The text was updated successfully, but these errors were encountered:
hholst80
changed the title
Spurios warning 'unknown argument ignored: lazytime'
Spurious warning 'unknown argument ignored: lazytime'
Aug 17, 2024
This flag is likely not supported by the FUSE mount frontend itself but supported by mount. If the lazy option is essential for user workflows (how can it be since its not working) then we should not use fusemount rather use mount directly. Or, let the user remount with the lazy flag.
The latest release of fuse-overlayfs (1.13-dev) prints out an annoying warning:
It seems hard coded somewhere, and should probably be removed, or at least be provisioned only after it has been validated to be compatible with the library/other APIs.
fuse-overlayfs/main.c
Line 5643 in 147609b
The text was updated successfully, but these errors were encountered: