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
open a new terminal and 'kill -9 xxxx' the mount process.
run umount /my/mountpoint
run infinit volume mount --name swarm-volume --cache --publish --mountpoint /my/mountpoint without --allow-root-creation and in foreground (no -d option)
stop the process with control-c or run umount /my/mountpoint (do not ls /my/mountpoint) from a different terminal session
then restart your service (again; no need for --allow-root-creation) as background service infinit volume mount --name alice-volume --cache --publish --mountpoint /my/mountpoint -d
done...
The text was updated successfully, but these errors were encountered:
--allow-root-creation should be run only once on one host, the root block is created when you use the mounted volumes for the first time.
see also: #15
However in when a mount is not cleaned up properly (kill -9 xxxx or a crash) and restart your mount you might run into the following situation.
tip: use
umount /my/mountpoint
to allow for proper house keepingNow an error occur when you try to use the mount...
So when you follow instruction and start the mount with the --allow-root-creation option and then use the volume you will get errors like these;
catch 22...
So how do we fix this?
We'll need to run the cleanup properly so this file is removed upon unmounting and it can be properly fetched from the slice-network if it exists.
steps
umount /my/mountpoint
infinit volume mount --name swarm-volume --cache --publish --mountpoint /my/mountpoint
without--allow-root-creation
and in foreground (no -d option)control-c
or runumount /my/mountpoint
(do notls /my/mountpoint
) from a different terminal sessioninfinit volume mount --name alice-volume --cache --publish --mountpoint /my/mountpoint -d
done...
The text was updated successfully, but these errors were encountered: