<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">On 20/01/20 2:13 pm, Roman wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFR=TBom0-o3yg6b-abvNZe6X1xC+kDdFPuKhM0keHOuNBV+HQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hello dear devs team!
<div><br>
</div>
<div>I'm sorry to write to you, not user-s list, but I really
would like to have DEV's opinion on my issue.</div>
<div><br>
</div>
<div>I've got multiple solutions running on old gluster versions
(same version per cluster, no mixed versions in same cluster):</div>
<div><br>
</div>
<div>Some of them are: 3.7.19, 3.10.9, 3.8.15</div>
<div><br>
</div>
<div>Yeah, I'm the geek who likes gluster from its beginning.
I've started with glusterfs for KVM (proxmox) and now am
running glusterfs for Tallinn University Academic Library
digitalization project (NAS) which runs fully at 1gbps without
any problems. One of gluster is running 250 TB storage and it
has to be extended, it is the DISTRIBUTED VOLUME :). I could
go the easy way and get 3.8.15 from old releases of gluster
repo, but i don't feel it to be the right way. What I would
really like to do is:</div>
<div>1. upgrade OS atm it is Debian GNU/Linux 8.10</div>
<div>2. upgrade the glusterfs</div>
<div><br>
</div>
<div>So my question is: what is the safe gluster version I could
upgrade to from my versions? I will do the offline upgrade.
And what my steps would be right? As I can see it:</div>
<div><br>
</div>
<div>1. shutdown gluster on all servers</div>
<div>2. upgrade os and gluster (change repo file for both os and
glusterfs version supported on that os and safe to upgrade to,
run apt-get dist upgrade)<br>
</div>
<div><br>
</div>
<div>As you understand, there is no possibility to backup that
ammount of data (the time it would take is not acceptable). We
have some data copied periodically to national archive, but
not all of it.</div>
<div><br>
</div>
<div>What do you think on this?</div>
</div>
</blockquote>
<p>As long as you are upgrading, it is better to use the latest
version (7.x). While nothing should go wrong, since 3.x is really
old, I'm not 100% sure if everything will be smooth post the
upgrade. The best way is to create a small 'test' setup (maybe a 1
brick volume with 1 client and some data) and try upgrading it to
7.x , bump up to the right op-version etc. and verify that every
thing works. If it does, then you can do the actual offline
upgrade in peace.<br>
</p>
<p>Hope this helps,</p>
<p>Ravi<br>
</p>
<blockquote type="cite"
cite="mid:CAFR=TBom0-o3yg6b-abvNZe6X1xC+kDdFPuKhM0keHOuNBV+HQ@mail.gmail.com">
<div dir="ltr">
<div>
<div><br>
</div>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Best regards,<br>
Roman.</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Community Meeting Calendar:
APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: <a class="moz-txt-link-freetext" href="https://bluejeans.com/441850968">https://bluejeans.com/441850968</a>
NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: <a class="moz-txt-link-freetext" href="https://bluejeans.com/441850968">https://bluejeans.com/441850968</a>
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>
<a class="moz-txt-link-freetext" href="https://lists.gluster.org/mailman/listinfo/gluster-devel">https://lists.gluster.org/mailman/listinfo/gluster-devel</a>
</pre>
</blockquote>
</body>
</html>