<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>So we migrated a number of VMs from a small Gluster 2+1A volume
to a newer cluster.</p>
<p>Then a few days later the client said he wanted an old forgotten
file that had been left behind on the the deprecated system. <br>
</p>
<p>However the arbiter and one of the brick nodes had been scraped,
leaving only a single gluster node. <br>
</p>
<p>The volume I need uses shards so I am not excited about having to
piece it back together.</p>
<p>I powered it up the single node and tried to mount the volume and
of course it refused to mount due to quorum and gluster volume
status shows the volume offline<br>
</p>
<p>In the past I had worked around this issue by disabling quorum,
but that was years ago, so I googled it and found list messages
suggesting the following:<br>
</p>
<p><span style="font-family:courier new,courier,monospace;"> <span
style="color:#008000;">gluster volume set VOL
cluster.quorum-type none<br>
</span> <span style="color:#008000;">gluster volume set VOL
cluster.server-quorum-type none</span></span> <br>
</p>
<p>However, the gluster 6.9 system refuses to accept those set
commands due to the quorum and spits out the set failed error.<br>
</p>
<p>So in modern Gluster, what is the preferred method for starting
and mounting a single node/volume that was once part of a actual
3 node cluster?</p>
<p>Thanks.<br>
</p>
<p>-wk<br>
</p>
<p><br>
</p>
</body>
</html>