search for: 0x00000000000000000000000000000001

...gluster* cmd.run 'getfattr -d -m . -e hex /bricks/brick1/gv0' glusterp2.graywitch.co.nz: getfattr: Removing leading '/' from absolute path names # file: bricks/brick1/gv0 security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.dht=0x000000010000000000000000ffffffff trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3 glusterp3.graywitch.co.nz: getfattr: Removing leading '/' from absolute path names # file: bricks/brick1/gv0 security.selinux=0x73797374656d5f753a6f626a65...

...n Status: Connected Number of entries: 1 [root at glusterp1 gv0]# getfattr -d -m . -e hex /bricks/brick1/gv0 getfattr: Removing leading '/' from absolute path names # file: bricks/brick1/gv0 security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.dht=0x000000010000000000000000ffffffff trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3 [root at glusterp1 gv0]# gluster volume info vol Volume vol does not exist [root at glusterp1 gv0]# gluster volume info gv0 Volume Name: gv0 Type: Replicate Volume ID: cfceb353-...

...ttr -d -m . -e hex >/bricks/brick1/gv0' >glusterp2.graywitch.co.nz: > getfattr: Removing leading '/' from absolute path names > # file: bricks/brick1/gv0 > >security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 > trusted.gfid=0x00000000000000000000000000000001 > trusted.glusterfs.dht=0x000000010000000000000000ffffffff > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3 >glusterp3.graywitch.co.nz: > getfattr: Removing leading '/' from absolute path names > # file: bricks/brick1/gv0 > >security.selinux=...

...ULE/filename.shareKey trusted.gfid=0x3b6c722cd6c64a4180fa028809671d63 trusted.gfid2path.9cb852a48fe5e361=0x38666131356462642d636435632d343930302d623838392d3066653766636534366131332f6e6361646d696e6973747261746f722e73686172654b6579 trusted.glusterfs.quota.8fa15dbd-cd5c-4900-b889-0fe7fce46a13.contri.1=0x00000000000000000000000000000001 trusted.pgfid.8fa15dbd-cd5c-4900-b889-0fe7fce46a13=0x00000001 # file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 trusted.glusterfs.dht=0x000000010000000000000000ffffffff trusted.glusterfs.quota.d...

...1/gv0' > >glusterp2.graywitch.co.nz: > > getfattr: Removing leading '/' from absolute path names > > # file: bricks/brick1/gv0 > > > >security.selinux=0x73797374656d5f753a6f626a6563 > 745f723a756e6c6162656c65645f743a733000 > > trusted.gfid=0x00000000000000000000000000000001 > > trusted.glusterfs.dht=0x000000010000000000000000ffffffff > > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3 > >glusterp3.graywitch.co.nz: > > getfattr: Removing leading '/' from absolute path names > > # file: bricks/brick1/gv0 &...

...areKey > trusted.gfid=0x3b6c722cd6c64a4180fa028809671d63 > trusted.gfid2path.9cb852a48fe5e361=0x38666131356462642d636435632d343930302d623838392d3066653766636534366131332f6e6361646d696e6973747261746f722e73686172654b6579 > trusted.glusterfs.quota.8fa15dbd-cd5c-4900-b889-0fe7fce46a13.contri.1=0x00000000000000000000000000000001 > trusted.pgfid.8fa15dbd-cd5c-4900-b889-0fe7fce46a13=0x00000001 > > # file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ > trusted.gfid=0x8fa15dbdcd5c4900b8890fe7fce46a13 > trusted.glusterfs.dht=0x000000010000000000000000ffffffff &...

...terp2.graywitch.co.nz: >> > getfattr: Removing leading '/' from absolute path names >> > # file: bricks/brick1/gv0 >> > >> >security.selinux=0x73797374656d5f753a6f626a6563745f723a756e >> 6c6162656c65645f743a733000 >> > trusted.gfid=0x00000000000000000000000000000001 >> > trusted.glusterfs.dht=0x000000010000000000000000ffffffff >> > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3 >> >glusterp3.graywitch.co.nz: >> > getfattr: Removing leading '/' from absolute path names >> > # file:...

Whatever repair happened has now finished but I still have this, I cant find anything so far telling me how to fix it. Looking at http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/heal-info-and-split-brain-resolution/ I cant determine what file? dir gvo? is actually the issue. [root at glusterp1 gv0]# gluster volume heal gv0 info split-brain Brick

...22cd6c64a4180fa028809671d63 > > > > trusted.gfid2path.9cb852a48fe5e361=0x38666131356462642d636435632d343930302d623838392d3066653766636534366131332f6e6361646d696e6973747261746f722e73686172654b6579 > > > > trusted.glusterfs.quota.8fa15dbd-cd5c-4900-b889-0fe7fce46a13.contri.1=0x00000000000000000000000000000001 > > > > trusted.pgfid.8fa15dbd-cd5c-4900-b889-0fe7fce46a13=0x00000001 > > > > file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ > > =================================================================================...

...gt;>> > getfattr: Removing leading '/' from absolute path names >>> > # file: bricks/brick1/gv0 >>> > >>> >security.selinux=0x73797374656d5f753a6f626a6563745f723a756e >>> 6c6162656c65645f743a733000 >>> > trusted.gfid=0x00000000000000000000000000000001 >>> > trusted.glusterfs.dht=0x000000010000000000000000ffffffff >>> > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3 >>> >glusterp3.graywitch.co.nz: >>> > getfattr: Removing leading '/' from absolute path names >>...

...9671d63 > > > > > > trusted.gfid2path.9cb852a48fe5e361=0x38666131356462642d636435632d343930302d623838392d3066653766636534366131332f6e6361646d696e6973747261746f722e73686172654b6579 > > > > > > trusted.glusterfs.quota.8fa15dbd-cd5c-4900-b889-0fe7fce46a13.contri.1=0x00000000000000000000000000000001 > > > > > > trusted.pgfid.8fa15dbd-cd5c-4900-b889-0fe7fce46a13=0x00000001 > > > > > > file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ > > > ========================================================...

On 05/15/2018 12:38 PM, mabi wrote: > Dear all, > > I have upgraded my replica 3 GlusterFS cluster (and clients) last Friday from 3.12.7 to 3.12.9 in order to fix this bug but unfortunately I notice that I still have exactly the same problem as initially posted in this thread. > > It looks like this bug is not resolved as I just got right now 3 unsynched files on my arbiter node

...3 >>>> >>>> trusted.gfid2path.9cb852a48fe5e361=0x38666131356462642d636435632d343930302d623838392d3066653766636534366131332f6e6361646d696e6973747261746f722e73686172654b6579 >>>> >>>> trusted.glusterfs.quota.8fa15dbd-cd5c-4900-b889-0fe7fce46a13.contri.1=0x00000000000000000000000000000001 >>>> >>>> trusted.pgfid.8fa15dbd-cd5c-4900-b889-0fe7fce46a13=0x00000001 >>>> >>>> file: data/myvolume-private/brick/dir1/dir2/dir3/dir4/dir5/dir6/dir7/dir8/dir9/dir10/OC_DEFAULT_MODULE/ >>>> ================================================...

Dear all, I have upgraded my replica 3 GlusterFS cluster (and clients) last Friday from 3.12.7 to 3.12.9 in order to fix this bug but unfortunately I notice that I still have exactly the same problem as initially posted in this thread. It looks like this bug is not resolved as I just got right now 3 unsynched files on my arbiter node like I used to do before upgrading. This problem started

Hi Kotresh, thanks for your repsonse... answers inside... best regards Dietmar Am 13.03.2018 um 06:38 schrieb Kotresh Hiremath Ravishankar: > Hi Dietmar, > > I am trying to understand the problem and have few questions. > > 1. Is trashcan enabled only on master volume? no, trashcan is also enabled on slave. settings are the same as on master but trashcan on slave is complete

...ersion=0x31000000000000005a39237200073206 trusted.gfid=0x7a36937d52fc4b55a93299e2328f02ba trusted.gfid2path.c076c6ac27a43012=0x30303030303030302d303030302d303030302d303030302d3030303030303030303030312f6665646f726132372e71636f7732 trusted.glusterfs.quota.00000000-0000-0000-0000-000000000001.contri.1=0x00000000000000000000000000000001 trusted.pgfid.00000000-0000-0000-0000-000000000001=0x00000001 I was expecting trusted.afr.virt_images-client-{1,2,3} on all bricks? > The changelog xattrs are named trusted.afr.virt_images-client-{1,2,3} in the > getxattr outputs you have provided. > Did you do a remove-brick and add-bri...

...39237200073206 > trusted.gfid=0x7a36937d52fc4b55a93299e2328f02ba > trusted.gfid2path.c076c6ac27a43012=0x30303030303030302d303030302d > 303030302d303030302d3030303030303030303030312f6665646f726132372e71636f7732 > trusted.glusterfs.quota.00000000-0000-0000-0000-000000000001.contri.1= > 0x00000000000000000000000000000001 > trusted.pgfid.00000000-0000-0000-0000-000000000001=0x00000001 > > I was expecting trusted.afr.virt_images-client-{1,2,3} on all bricks? > >From AFR-V2 we do not have self blaming attrs. So you will see a brick blaming other bricks only. For example brcik1 can blame brick2 & br...

Hey, Can you give us the volume info output for this volume? Why are you not able to get the xattrs from arbiter brick? It is the same way as you do it on data bricks. The changelog xattrs are named trusted.afr.virt_images-client-{1,2,3} in the getxattr outputs you have provided. Did you do a remove-brick and add-brick any time? Otherwise it will be trusted.afr.virt_images-client-{0,1,2} usually.

...;> trusted.gfid=0x7a36937d52fc4b55a93299e2328f02ba >> >> trusted.gfid2path.c076c6ac27a43012=0x30303030303030302d303030302d303030302d303030302d3030303030303030303030312f6665646f726132372e71636f7732 >> >> trusted.glusterfs.quota.00000000-0000-0000-0000-000000000001.contri.1=0x00000000000000000000000000000001 >> trusted.pgfid.00000000-0000-0000-0000-000000000001=0x00000001 >> >> I was expecting trusted.afr.virt_images-client-{1,2,3} on all bricks? > > From AFR-V2 we do not have self blaming attrs. So you will see a brick > blaming other bricks only. > For example brcik1 ca...

...c4b55a93299e2328f02ba > >> > >> trusted.gfid2path.c076c6ac27a43012=0x30303030303030302d303030302d > 303030302d303030302d3030303030303030303030312f6665646f726132372e71636f7732 > >> > >> trusted.glusterfs.quota.00000000-0000-0000-0000-000000000001.contri.1= > 0x00000000000000000000000000000001 > >> trusted.pgfid.00000000-0000-0000-0000-000000000001=0x00000001 > >> > >> I was expecting trusted.afr.virt_images-client-{1,2,3} on all bricks? > > > > From AFR-V2 we do not have self blaming attrs. So you will see a brick > > blaming other bricks on...