<div dir="ltr"><div>What is the endianness of the armhf CPU ?</div><div>Are you running a 32bit or 64bit Operating System ?</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 3, 2018 at 9:51 AM, Fox <span dir="ltr"><<a href="mailto:foxxz.net@gmail.com" target="_blank">foxxz.net@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Just wondering if anyone else is running into the same behavior with disperse volumes described below and what I might be able to do about it.</div><div><br></div><div>I am using ubuntu 18.04LTS on Odroid HC-2 hardware (armhf) and have installed gluster 4.1.2 via PPA. I have 12 member nodes each with a single brick. I can successfully create a working volume via the command:</div><div><br></div><div>gluster volume create testvol1 disperse 12 redundancy 4 gluster01:/exports/sda/brick1/<wbr>testvol1 gluster02:/exports/sda/brick1/<wbr>testvol1 gluster03:/exports/sda/brick1/<wbr>testvol1 gluster04:/exports/sda/brick1/<wbr>testvol1 gluster05:/exports/sda/brick1/<wbr>testvol1 gluster06:/exports/sda/brick1/<wbr>testvol1 gluster07:/exports/sda/brick1/<wbr>testvol1 gluster08:/exports/sda/brick1/<wbr>testvol1 gluster09:/exports/sda/brick1/<wbr>testvol1 gluster10:/exports/sda/brick1/<wbr>testvol1 gluster11:/exports/sda/brick1/<wbr>testvol1 gluster12:/exports/sda/brick1/<wbr>testvol1</div><div><br></div><div>And start the volume:</div><div></div><div>gluster volume start testvol1<br></div><div><br></div><div>Mounting the volume on an x86-64 system it performs as expected.</div><div><br></div><div>Mounting the same volume on an armhf system (such as one of the cluster members) I can create directories but trying to create a file I get an error and the file system unmounts/crashes:</div><div>root@gluster01:~# mount -t glusterfs gluster01:/testvol1 /mnt<br>root@gluster01:~# cd /mnt<br>root@gluster01:/mnt# ls<br>root@gluster01:/mnt# mkdir test<br>root@gluster01:/mnt# cd test<br></div><div>root@gluster01:/mnt/test# cp /root/notes.txt ./<br>cp: failed to close './notes.txt': Software caused connection abort<br>root@gluster01:/mnt/test# ls<br>ls: cannot open directory '.': Transport endpoint is not connected</div><div><br></div><div>I get many of these in the glusterfsd.log:<br></div><div>The message "W [MSGID: 101088] [common-utils.c:4316:gf_<wbr>backtrace_save] 0-management: Failed to save the backtrace." repeated 100 times between [2018-08-03 04:06:39.904166] and [2018-08-03 04:06:57.521895]<br></div><div><br></div><div><br></div><div>Furthermore, if a cluster member ducks out (reboots, loses connection, etc) and needs healing the self heal daemon logs messages similar to that above and can not heal - no disk activity (verified via iotop) though very high CPU usage and the volume heal info command indicates the volume needs healing.</div><div><br></div><div><br></div><div>I tested all of the above in virtual environments using x86-64 VMs and could self heal as expected.</div><div><br></div><div>Again this only happens when using disperse volumes. Should I be filing a bug report instead?<br></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Milind<br><br></div></div></div></div>
</div>