Hi Anant,
Do you use the fuse client in the container ?Wouldn't it be more reasonable to
mount the fuse and then use bind mount to provide access to the container ?
Best Regards,Strahil Nikolov
On Fri, Feb 16, 2024 at 15:02, Anant Saraswat
wrote: Okay, I understand. Yes, it would be
Hi Strahil,
Yes, we mount the fuse to the physical host and then use bind mount to provide
access to the container.
The same physical host also runs the gluster server. Therefore, when we stop
gluster using 'stop-all-gluster-processes.sh' on the physical host, it kills
the fuse mount and
Hello Everyone,
We are mounting this external Gluster volume (dc.local:/docker_config) for
docker configuration on one of the Gluster servers. When I ran the
stop-all-gluster-processes.sh script, I wanted to stop all gluster
server-related processes on the server, but not to unmount the
No. If the script is used to update the GlusterFS packages in the node, then we
need to stop the client processes as well (Fuse client is `glusterfs` process.
`ps ax | grep glusterfs`).
The default behaviour can't be changed, but the script can be enhanced by
adding a new option
Okay, I understand. Yes, it would be beneficial to include an option for
skipping the client processes. This way, we could utilize the
'stop-all-gluster-processes.sh' script with that option to stop the gluster
server process while retaining the fuse mounts.
