Tell us more about this new feature.
Currently, the latest version still doesn't work well with automatic mounting (autofs or systemd).
It fails with following error
Jun 26 14:15:52 node000 mount-s3[785767]: [INFO] ThreadId(01) mountpoint_s3::run: mount-s3 1.22.3
Jun 26 14:15:52 node000 automount[785739]: do_spawn: >> Error: Failed to create mount point
Jun 26 14:15:52 node000 automount[785739]: do_spawn: >> Caused by:
Jun 26 14:15:52 node000 automount[785739]: do_spawn: >> mount point /logs/archive is already mounted
Jun 26 14:15:52 node000 automount[785739]: do_spawn: >> Error: Failed to create mount process
Jun 26 14:15:52 node000 automount[785739]: mount(generic): failed to mount mount-s3#logarch-prod (type fuse) on /logs/archive
Jun 26 14:15:52 node000 automount[785739]: lookup_mount: lookup(file): looking up /logs/archive
Jun 26 14:15:52 node000 automount[785739]: dev_ioctl_send_fail: token = 47
Jun 26 14:15:52 node000 automount[785739]: failed to mount /logs/archive
The idea is to achieve seamless automatic mounting of buckets while avoiding resource usage when the bucket contents are not being accessed.
Tell us more about this new feature.
Currently, the latest version still doesn't work well with automatic mounting (autofs or systemd).
It fails with following error
The idea is to achieve seamless automatic mounting of buckets while avoiding resource usage when the bucket contents are not being accessed.