search for: b015

...port/socket.so(+0xa79d)[0x7f8d088e179d] /usr/lib64/libglusterfs.so.0[0x388968b2f0] /lib64/libpthread.so.0[0x34a2007aa1] /lib64/libc.so.6(clone+0x6d)[0x34a1ce8aad] [root at mseas-data2 glusterfs]# gluster volume info Volume Name: data-volume Type: Distribute Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 Status: Started Number of Bricks: 2 Transport-type: tcp Bricks: Brick1: mseas-data2:/mnt/brick1 Brick2: mseas-data2:/mnt/brick2 Options Reconfigured: nfs.export-volumes: on nfs.disable: off performance.readdir-ahead: on diagnostics.brick-sys-log-level: WARNING nfs.exports-a...

...> kernel errors > > could result from many things including drive > > itself, cable or > > ide-controller. Let's take a closer look. > > > > > > > smartctl -a /dev/hda reports: > > > Serial Number: 01043113 > > > Firmware Version: B015 > > > Device is: Not in smartctl database [for > > > details use: -P showall] > > > ATA Version is: 4 > > > > ATA version 4 is pretty old. > > Also notice the not in smartctl database line. > > Are you using the latest version of smartmo...

...gt; > /lib64/libpthread.so.0[0x34a2007aa1] > > /lib64/libc.so.6(clone+0x6d)[0x34a1ce8aad] > > > > > > > [root at mseas-data2 glusterfs]# gluster volume info > > Volume Name: data-volume > > Type: Distribute > > Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 > > Status: Started > > Number of Bricks: 2 > > Transport-type: tcp > > Bricks: > > Brick1: mseas-data2:/mnt/brick1 > > Brick2: mseas-data2:/mnt/brick2 > > Options Reconfigured: > > nfs.export-volumes: on > > nfs.disable: o...

...t: Re: [Gluster-users] Slow write times to gluster disk >> >> >> Hi Ben, >> >> Here is the output: >> >> [root at mseas-data2 ~]# gluster volume info >> >> Volume Name: data-volume >> Type: Distribute >> Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 >> Status: Started >> Number of Bricks: 2 >> Transport-type: tcp >> Bricks: >> Brick1: mseas-data2:/mnt/brick1 >> Brick2: mseas-data2:/mnt/brick2 >> Options Reconfigured: >> nfs.exports-auth-enable: on >> diagnostics.brick-sys-log-l...

...Name: data-volume > >>>>>>>>> Type: Distribute > >>>>>>>>> Volume ID: > >>>>>>>>> c162161e-2a2d-4dac-b015-f31fd89ceb18 > >>>>>>>>> Status: Started > >>>>>>>>> Number of Bricks: 2 > >>>>>>>>> Transport-type:...

...luster disk >>> >>> >>> Hi Ben, >>> >>> Here is the output: >>> >>> [root at mseas-data2 ~]# gluster volume info >>> >>> Volume Name: data-volume >>> Type: Distribute >>> Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 >>> Status: Started >>> Number of Bricks: 2 >>> Transport-type: tcp >>> Bricks: >>> Brick1: mseas-data2:/mnt/brick1 >>> Brick2: mseas-data2:/mnt/brick2 >>> Options Reconfigured: >>> nfs.exports-auth-enable: on >...

...volume >>>>>>>>>>> Type: Distribute >>>>>>>>>>> Volume ID: >>>>>>>>>>> c162161e-2a2d-4dac-b015-f31fd89ceb18 >>>>>>>>>>> Status: Started >>>>>>>>>>> Number of Bricks: 2 >>>>>>>>>>> Tran...

...Monday, June 12, 2017 5:18:07 PM > Subject: Re: [Gluster-users] Slow write times to gluster disk > > > Hi Ben, > > Here is the output: > > [root at mseas-data2 ~]# gluster volume info > > Volume Name: data-volume > Type: Distribute > Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 > Status: Started > Number of Bricks: 2 > Transport-type: tcp > Bricks: > Brick1: mseas-data2:/mnt/brick1 > Brick2: mseas-data2:/mnt/brick2 > Options Reconfigured: > nfs.exports-auth-enable: on > diagnostics.brick-sys-log-level: WARNING > performance.readd...

...ead.so.0[0x34a2007aa1] > > /lib64/libc.so.6(clone+0x6d)[0x34a1ce8aad] > > > > > > > [root at mseas-data2<mailto:root at mseas-data2> glusterfs]# gluster volume info > > Volume Name: data-volume > > Type: Distribute > > Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 > > Status: Started > > Number of Bricks: 2 > > Transport-type: tcp > > Bricks: > > Brick1: mseas-data2:/mnt/brick1 > > Brick2: mseas-data2:/mnt/brick2 > > Options Reconfigured: > > nfs.export-volumes: on > > nfs.disable: off > &...

...gt; >>>> Here is the output: >>>> >>>> [root at mseas-data2 ~]# gluster volume info >>>> >>>> Volume Name: data-volume >>>> Type: Distribute >>>> Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 >>>> Status: Started >>>> Number of Bricks: 2 >>>> Transport-type: tcp >>>> Bricks: >>>> Brick1: mseas-data2:/mnt/brick1 >>>> Brick2: mseas-data2:/mnt/brick2 >>...

...t: Re: [Gluster-users] Slow write times to gluster disk >> >> >> Hi Ben, >> >> Here is the output: >> >> [root at mseas-data2 ~]# gluster volume info >> >> Volume Name: data-volume >> Type: Distribute >> Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 >> Status: Started >> Number of Bricks: 2 >> Transport-type: tcp >> Bricks: >> Brick1: mseas-data2:/mnt/brick1 >> Brick2: mseas-data2:/mnt/brick2 >> Options Reconfigured: >> nfs.exports-auth-enable: on >> diagnostics.brick-sys-log-l...

...luster disk >>> >>> >>> Hi Ben, >>> >>> Here is the output: >>> >>> [root at mseas-data2 ~]# gluster volume info >>> >>> Volume Name: data-volume >>> Type: Distribute >>> Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18 >>> Status: Started >>> Number of Bricks: 2 >>> Transport-type: tcp >>> Bricks: >>> Brick1: mseas-data2:/mnt/brick1 >>> Brick2: mseas-data2:/mnt/brick2 >>> Options Reconfigured: >>> nfs.exports-auth-enable: on >...

...tartlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory finddcs: response 0 at '131.192.176.6' finddcs: response 1 at '2002:83c0:b007::83c0:b007' finddcs: response 2 at '2002:83c0:b006::83c0:b006' finddcs: response 3 at '2002:83c0:b015::83c0:b015' finddcs: response 4 at '2002:83c0:b008::83c0:b008' finddcs: performing CLDAP query on 131.192.176.6 finddcs: Found matching DC 131.192.176.6 with server_type=0x000011fc >>>> Very frustrating -Barry Adkins

Hai, I had a quick look. Barry, can you get this script and run it. https://raw.githubusercontent.com/thctlo/samba4/master/samba-collect-debug-info.sh Then post the results to the list. It collects all info i need to have a better look. I have a few ideas, this might be a resolving order problem, i've based on the errors below. Can you also post the output of bind from the point its

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...a-60a988eb9358/3C932713B7E92E0CE6E1E9E44DD6BC6BEA258BC4 (d18f2279-c0aa-4166-aca8-e89f2a8af54d) on home-client-2 [2017-10-25 10:14:18.999093] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/026E611ECAF38F57B015F9D9F298A277EC1BFA0B (cd42f792-1031-4e81-bace-80f612cdbc42) on home-client-2 [2017-10-25 10:14:19.027511] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/37B12C43F174F70408DA41A31DAF4B188768D060 (2241dec0-...