[Gluster-users] Shared Storage is unmount after stopping glusterd

[David Spisla]

Sure, I will do that the next time shared_storage is unmount after stopping
glusterd

Am Fr., 9. Nov. 2018 um 10:23 Uhr schrieb Rafi Kavungal Chundattu Parambil <
rkavunga at redhat.com>:

> Hi David Spisla,
>
> gluster_shared_storage works just like yet another volume(There are some
> special handling related to authentication). So bringing down a glusterd
> node shouldn't have lead to unmount of the volume.
>
> Can you please share the mount log, brick logs at time when you stopped
> glusterd. Also make sure your shared storage bricks up and running.
>
> Regards
> Rafi KC
>
> ----- Original Message -----
> From: "David Spisla" <spisla80 at gmail.com>
> To: gluster-users at gluster.org
> Sent: Tuesday, November 6, 2018 3:25:18 PM
> Subject: [Gluster-users] Shared Storage is unmount after stopping glusterd
>
> Dear Gluster Community,
> I have a v4.1.5 4-node-cluster with SLES15 machines. The last time I
> observe that after stopping glusterd with
> $ sudo systemctl stop glusterd
>
> sometimes also the FUSE mount of the shared_storage on the same node is
> unmount but shared_storage ist still in the volume list. I mean really
> "sometimes" because it is not reproducible in a deterministic way and I am
> not sure if there is really a dependency between stopping glusterd and
> shared_storage.
>
> What is the expected behaviour if stopping glusterd? In my opinion all
> volumes included shared_storage should still have FUSE mounts.
>
> Regards
> David Spisla
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20181109/3b3a8ded/attachment.html>