similar to: Problem migration 3.7.6 to 3.13.2

Hi Daniele, Do you mean that the df -h output is incorrect for the volume post the upgrade? If yes and the bricks are on separate partitions, you might be running into [1]. Can you search for the string "option shared-brick-count" in the files in /var/lib/glusterd/vols/<volumename> and let us know the value? The workaround to get this working on the cluster is available in [2].

Thanks for replay. I founded this values datastore_temp.serda1.glusterfs-p1-b1.vol: option shared-brick-count 2 datastore_temp.serda1.glusterfs-p2-b2.vol: option shared-brick-count 2 datastore_temp.serda2.glusterfs-p1-b1.vol: option shared-brick-count 0 datastore_temp.serda2.glusterfs-p2-b2.vol: option shared-brick-count 0 I need to change the values of serda2 node?! 2018-02-23

Whem I try to run healin volume i have this log errors and 3221 file not healing: [2018-02-24 15:32:00.915219] W [socket.c:3216:socket_connect] 0-glusterfs: Error disabling sockopt IPV6_V6ONLY: "Protocollo non disponibile" [2018-02-24 15:32:00.915854] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2018-02-24 15:32:01.925714] E

When I run gluster v heal datastore full errror into log is gfapi: Error disabling sockopt IPV6_V6ONLY The brick are up. Version is 3.13.2 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180223/44c58392/attachment.html>

On 05/09/2018 09:02 AM, Roman Serbski wrote: > On Wed, May 9, 2018 at 1:22 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: >> >> That's certainly true. The issue hasn't been fixed in any version of >> gluster yet. >> >> You can help moving it along by voting +1 on >> https://review.gluster.org/19974 > > Will do -- thanks! >

The Gluster community is pleased to announce the release of Gluster 3.13.2 (packages available at [1]). Release notes for the release can be found at [2]. * FIXED: Expanding a gluster volume that is sharded may cause file corruption Thanks, Gluster community [1] Packages: https://download.gluster.org/pub/gluster/glusterfs/3.13/3.13.2/ [2] Release notes:

On Tue, May 8, 2018 at 11:34 AM, Roman Serbski <mefystofel at gmail.com> wrote: > # gdb gluster > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the

On Wed, May 9, 2018 at 1:22 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > That's certainly true. The issue hasn't been fixed in any version of > gluster yet. > > You can help moving it along by voting +1 on > https://review.gluster.org/19974 Will do -- thanks! > Based on that gdb bt you can try applying this patch too >

On Sat, Feb 8, 2014 at 2:58 AM, Daniel J Blueman <daniel at quora.org> wrote: > Hi guys, > > With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm > seeing significant graphical corruption and later unrecoverable GPU > lockup, accompanied by thousands of ILLEGAL_MTHD or related kernel > messages [1]. I see similar issues on 3.12 also. > > Is there any

On 05/09/2018 05:44 AM, Roman Serbski wrote: > On Tue, May 8, 2018 at 11:34 AM, Roman Serbski <mefystofel at gmail.com> wrote: >> # gdb gluster >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 Free Software Foundation, Inc. >> GDB is free software, covered by the GNU General Public License, and you are >> welcome to change it and/or distribute copies of it under

On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: > Interestingly, there was graphical failure booting 3.6.11, even > nvidia-current fails to initialise, but these two issues could be due > to running the Xorg stack in Ubuntu 14.04 pre-release. Using > nouveau.noaccel=1 works great for the first X session, but after > logging out, lightdm and the

On Sat, Feb 22, 2014 at 10:45 PM, Daniel J Blueman <daniel at quora.org> wrote: > On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >>> Interestingly, there was graphical failure booting 3.6.11, even >>> nvidia-current fails to initialise, but these

On Mon, May 7, 2018 at 9:19 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > > See https://review.gluster.org/19974 Many thanks Kaleb. Your patch did the trick and I did manage to compile, however I get a Segmentation fault when trying to execute gluster. I'm using the following options to configure (taken from the glusterfs 3.11.1 port in the FreeBSD port repository):

On 05/07/2018 04:29 AM, Roman Serbski wrote: > Hello, > > Has anyone managed to successfully compile the latest 3.13.2 under > FreeBSD 11.1? ./autogen.sh and ./configure seem to work but make > fails: See https://review.gluster.org/19974 3.13 reached EOL with 4.0. There will be a fix posted for 4.0 soon. In the mean time I believe your specific problem with 3.13.2 should be

Hi Stefan, There is a known issue with gluster 3.12.x builds (see [1]) so you may be running into this. Please take a look at [1] and try out the workaround provided in the comments. Regards, Nithya [1] https://bugzilla.redhat.com/show_bug.cgi?id=1517260 On 9 March 2018 at 13:37, Stefan Solbrig <stefan.solbrig at ur.de> wrote: > Dear all, > > I have a problem with df after

Hi guys, With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm seeing significant graphical corruption and later unrecoverable GPU lockup, accompanied by thousands of ILLEGAL_MTHD or related kernel messages [1]. I see similar issues on 3.12 also. Is there any debugging or testing I can do to help diagnose this? Many thanks, Daniel --- [1] http://quora.org/nouveau-dmesg.txt

On 8 February 2014 16:33, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 2:58 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Hi guys, >> >> With a GeForce 320M GPU running linux 3.13.2 and Xorg 1.15.0, I'm >> seeing significant graphical corruption and later unrecoverable GPU >> lockup, accompanied by thousands of

Hello, Has anyone managed to successfully compile the latest 3.13.2 under FreeBSD 11.1? ./autogen.sh and ./configure seem to work but make fails: Making all in src CC glfs.lo cc: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument] cc: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument] fatal

This patch is dependant on the previously submitted storage admin patch.

On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Interestingly, there was graphical failure booting 3.6.11, even >> nvidia-current fails to initialise, but these two issues could be due >> to running the Xorg stack in Ubuntu 14.04 pre-release. Using >>