<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><i><font size="2">Hello,</font></i><br><i><font color="#336666" size="2">We are using
GlusterFS 3.4.0 and we have a replicated volume with one brick each on two
real-time servers. For certain maintenance purposes, it may be desirable to
periodically reboot them. During said reboots, we wish to umount the brick
residing on it. However, umount fails (as expected),
because of the GlusterFS threads that are using it. We thought of the following
ways to counter this:</font></i><br><br><i><font color="#336666" size="2">a) Stop
the volume, thereby causing its GlusterFS threads to terminate. However, this
will mean that the other server would not be able to access the volume, which
will be a problem.</font></i><br><br><i><font color="#336666" size="2">b) Kill the
glusterFS threads on the volume, thereby allowing umount to proceed. However, I
am given to understand that this method is not very graceful, and may lead to
data loss in case some local modifications have not synced onto the other
server.</font></i><br><br><i><font color="#336666" size="2">c) Delete the brick from
the volume, remove its "trusted.glusterfs.volume-id", and then re-add it once
the server comes back up. </font></i><br><br><i><font color="#336666" size="2">Could you help me with some advice on what would be the best way to do it?</font></i></div><div style="color: rgb(0, 0, 0); font-size: 13px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: italic;"><i><font color="#336666" size="2"><br></font></i></div><div style="color: rgb(51, 102, 102); font-size: 13px; font-family: 'times new roman', 'new york', times, serif; background-color: transparent; font-style: italic;"><i><font color="#336666" size="2">Thanks in
advance for answering this!</font></i><br></div></div></body></html>