<div dir="ltr"><div><div><div><div>Neil I don;t know if this is adequate but I did run a simple smoke test today on the 3.12.3-1 bits. I installed the 3.12.3-1 but on 3 fresh install Centos 7 VMs<br><br></div>created a 2G image files and wrote a xfs files system on them on each system<br><br></div>mount each under /export/brick1, and created /export/birck1/test on each node.<br></div>probes the two other systems from one node (a). abd created a replica 3 volume using the bricks at export/brick1/test on each node.<br><br></div><div>started the volume and mounted it under /mnt/gluster test on nodes a.<br><br></div><div>did some brief tests using dd into the mount point on node a, all seemed fine - no errors nothing unexpected.<br><br><br></div><div><br><br></div><div><br></div><div><div><div><br><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 23 October 2017 at 17:42, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Oct 23, 2017 at 02:12:53PM -0400, Alastair Neil wrote:<br>
> Any idea when these packages will be in the CentOS mirrors? there is no<br>
> sign of them on <a href="http://download.gluster.org" rel="noreferrer" target="_blank">download.gluster.org</a>.<br>
<br>
</span>We're waiting for someone other than me to test the new packages at<br>
least a little. Installing the packages and run something on top of a<br>
Gluster volume is already sufficient, just describe a bit what was<br>
tested. Once a confirmation is sent that it works for someone, we can<br>
mark the packages for releasing to the mirrors.<br>
<br>
Getting the (unsigned) RPMs is easy, run this on your test environment:<br>
<br>
# yum --enablrepo=centos-gluster312-<wbr>test update glusterfs<br>
<br>
This does not restart the brick processes so I/O is not affected with<br>
the installation. Make sure to restart the processes (or just reboot)<br>
and do whatever validation you deem sufficient.<br>
<br>
Thanks,<br>
Niels<br>
<div><div class="h5"><br>
<br>
><br>
> On 13 October 2017 at 08:45, Jiffin Tony Thottan <<a href="mailto:jthottan@redhat.com">jthottan@redhat.com</a>><br>
> wrote:<br>
><br>
> > The Gluster community is pleased to announce the release of Gluster 3.12.2<br>
> > (packages available at [1,2,3]).<br>
> ><br>
> > Release notes for the release can be found at [4].<br>
> ><br>
> > We still carry following major issues that is reported in the<br>
> > release-notes as follows,<br>
> ><br>
> > 1.) - Expanding a gluster volume that is sharded may cause file corruption<br>
> ><br>
> > Sharded volumes are typically used for VM images, if such volumes are<br>
> > expanded or possibly contracted (i.e add/remove bricks and rebalance) there<br>
> > are reports of VM images getting corrupted.<br>
> ><br>
> > The last known cause for corruption (Bug #1465123) has a fix with this<br>
> > release. As further testing is still in progress, the issue is retained as<br>
> > a major issue.<br>
> ><br>
> > Status of this bug can be tracked here, #1465123<br>
> ><br>
> ><br>
> > 2 .) Gluster volume restarts fail if the sub directory export feature is<br>
> > in use. Status of this issue can be tracked here, #1501315<br>
> ><br>
> > 3.) Mounting a gluster snapshot will fail, when attempting a FUSE based<br>
> > mount of the snapshot. So for the current users, it is recommend to only<br>
> > access snapshot via<br>
> ><br>
> > ".snaps" directory on a mounted gluster volume. Status of this issue can<br>
> > be tracked here, #1501378<br>
> ><br>
> > Thanks,<br>
> > Gluster community<br>
> ><br>
> ><br>
> > [1] <a href="https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.2/" rel="noreferrer" target="_blank">https://download.gluster.org/<wbr>pub/gluster/glusterfs/3.12/3.<wbr>12.2/</a><br>
</div></div>> > <<a href="https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.1/" rel="noreferrer" target="_blank">https://download.gluster.org/<wbr>pub/gluster/glusterfs/3.12/3.<wbr>12.1/</a>><br>
> > [2] <a href="https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12" rel="noreferrer" target="_blank">https://launchpad.net/~<wbr>gluster/+archive/ubuntu/<wbr>glusterfs-3.12</a><br>
> > <<a href="https://launchpad.net/%7Egluster/+archive/ubuntu/glusterfs-3.11" rel="noreferrer" target="_blank">https://launchpad.net/%<wbr>7Egluster/+archive/ubuntu/<wbr>glusterfs-3.11</a>><br>
<span class="">> > [3] <a href="https://build.opensuse.org/project/subprojects/home:glusterfs" rel="noreferrer" target="_blank">https://build.opensuse.org/<wbr>project/subprojects/home:<wbr>glusterfs</a><br>
> ><br>
> > [4] Release notes: <a href="https://gluster.readthedocs" rel="noreferrer" target="_blank">https://gluster.readthedocs</a>.<br>
> > io/en/latest/release-notes/3.<wbr>12.2/<br>
</span>> > <<a href="https://gluster.readthedocs.io/en/latest/release-notes/3.11.3/" rel="noreferrer" target="_blank">https://gluster.readthedocs.<wbr>io/en/latest/release-notes/3.<wbr>11.3/</a>><br>
<div class="HOEnZb"><div class="h5">> ><br>
> > ______________________________<wbr>_________________<br>
> > Gluster-devel mailing list<br>
> > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
> ><br>
<br>
> ______________________________<wbr>_________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
<br>
</div></div></blockquote></div><br></div>