search for: bd3d

Attached is the heal log for the volume as well as the shd log. >> Run these commands on all the bricks of the replica pair to get the attrs set on the backend. [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 getfattr: Removing leading '/' from absolute path names # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.gv0-cl...

...ched is the heal log for the volume as well as the shd log. > > >> Run these commands on all the bricks of the replica pair to get the > attrs set on the backend. > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . > /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > getfattr: Removing leading '/' from absolute path names > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > security.selinux=0x73797374656d5f753a6f626a6563 > 745f723a756e6c6162656c65645f743a733000 > trusted.afr.dirty=0x00000000000000000...

Hi Matt, Run these commands on all the bricks of the replica pair to get the attrs set on the backend. On the bricks of first replica set: getfattr -d -e hex -m . <brick path>/.glusterfs/10/86/ 108694db-c039-4b7c-bd3d-ad6a15d811a2 On the fourth replica set: getfattr -d -e hex -m . <brick path>/.glusterfs/ e0/c5/e0c56bf7-8bfe-46ca-bde1-e46b92d33df3 Also run the "gluster volume heal <volname>" once and send the shd log. And the output of "gluster volume heal <volname> info split-...

...al log for the volume as well as the shd log. > > > > Run these commands on all the bricks of the replica pair to get > > > the attrs set on the backend. > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . > /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > getfattr: Removing leading '/' from absolute path names > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d- > ad6a15d811a2 > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c > 65645f743a733000 > trusted.afr.dirty=0x00000000000...

...Matt Waymack wrote: Attached is the heal log for the volume as well as the shd log. Run these commands on all the bricks of the replica pair to get the attrs set on the backend. [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 getfattr: Removing leading '/' from absolute path names # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.g...

...hed is the heal log for the volume as well as the shd log. > > > > Run these commands on all the bricks of the replica pair to get the attrs set on the backend. > > > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > getfattr: Removing leading '/' from absolute path names > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 > trusted.afr.dirty=0x00000000000000000000000...

...ca pair to > > > > > get the attrs set on the backend. > > > > > > > > > > > > > > > > > > > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . > > > /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > > > getfattr: Removing leading '/' from absolute path names > > > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d- > > > ad6a15d811a2 > > > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162 > > > 656c656...

...ll as the shd log. > > > > > > > > Run these commands on all the bricks of the replica pair to get the attrs set on the backend. > > > > > > > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > > getfattr: Removing leading '/' from absolute path names > > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2 > > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 > > trusted.afr.dirty=0x000...

...> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . > > > > > /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d- > > > > > ad6a15d811a2 > > > > > getfattr: Removing leading '/' from absolute path names > > > > > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d- > > > > > ad6a15d811a2 > > > > > security.selinux=0x737...

...> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > [root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . > > > > > /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d- > > > > > ad6a15d811a2 > > > > > getfattr: Removing leading '/' from absolute path names > > > > > # file: exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d- > > > > > ad6a15d811a2 > > > > > security.selinux=0x737...

...gv0 Brick11: tpc-cent-glus2-081017:/exp/b4/gv0 Brick12: tpc-arbiter1-100617:/exp/b4/gv0 (arbiter) Options Reconfigured: nfs.disable: on transport.address-family: inet [root at tpc-cent-glus1-081017 ~]# gluster volume heal gv0 info Brick tpc-cent-glus1-081017:/exp/b1/gv0 <gfid:108694db-c039-4b7c-bd3d-ad6a15d811a2> <gfid:6d5ade20-8996-4de2-95d5-20ef98004742> <gfid:bc6cdc3d-5c46-4597-a7eb-282b21e9bdd5> <gfid:3c2ff4d1-3662-4214-8f21-f8f47dbdbf06> <gfid:053e2fb1-bc89-476e-a529-90dffa39963c> <removed to save scrolling> Status: Connected Number of entries: 118 Bric...

Hi Matt, The files might be in split brain. Could you please send the outputs of these? gluster volume info <volname> gluster volume heal <volname> info And also the getfattr output of the files which are in the heal info output from all the bricks of that replica pair. getfattr -d -e hex -m . <file path on brick> Thanks & Regards Karthik On 16-Oct-2017 8:16 PM,

Hi all, For months now I''ve been using Puppet with PuppetDB backend to manage my Nagios configs. We now have 1200+ services being checked and including servicedependency, host, hostdependency, command and other Nagios resources being managed, that''s about 3000 resources in total. Unfortunately this means the monitoring server takes about 8 minutes to perform a Puppet run.