<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 9, 2019 at 12:23 AM Alexander Iliev <<a href="mailto:ailiev%2Bgluster@mamul.org">ailiev+gluster@mamul.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I am running a GlusterFS server 6.3 on three Ubuntu 18.04 nodes <br>
installed from the <a href="https://launchpad.net/~gluster" rel="noreferrer" target="_blank">https://launchpad.net/~gluster</a> PPA.<br>
<br>
I tried upgrading to 6.5 today and ran into an issue with the first (and <br>
only) node that has been upgraded so far. When I rebooted the node the <br>
underlying brick filesystems failed to mount because of a `pvscan` <br>
process timing out on boot.<br>
<br>
I did some experimenting and the issue seems to be that on reboot the <br>
glusterfsd processes (that expose the bricks as far as I understand) are <br>
not being shut down which leads to the underlying filesystems show up as <br>
busy and not getting properly unmounted.<br>
<br>
Then I found out that `systemctl stop glusterd.service` doesn't stop the <br>
brick processes by design and it also seems that for Fedora/RHEL this <br>
has been worked around by having a separate `glusterfsd.service` unit <br>
that only acts on shutdown.<br>
<br>
This however does not seem to be the case on Ubuntu and I can't figure <br>
out what is the expected flow there.<br>
<br>
So I guess my question is - is this normal/expected behaviour on Ubuntu? <br>
How is one supposed to set things up so that bricks get properly <br>
unmounted on reboot and properly mounted at startup?<br>
<br>
I am also considering migrating from Ubuntu to CentOS now as the <br>
upstream support seems much better there. If I decide to switch can I <br>
re-use the existing bricks or do I need to spin up a clean node, join <br>
the cluster and get the data synced to it?<br>
<br></blockquote><div>I can only answer this part for now. If your bricks can be accessed directly on CentOS (xfs/ext4 or anything) after installing new OS, it should just work fine with GlusterFS too after migration.. The challenge will be with content of /var/lib/glusterd (and IP addresses etc), which you need to handle properly.</div><div><br></div><div>Regards,</div><div>Amar</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thanks!<br>
<br>
Best regards,<br>
-- <br>
alexander iliev<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div></div>