search for: xattrop

...d Number of entries: 0 Brick node2.domain.tld:/data/myvolume/brick <gfid:29e0d13e-1217-41cc-9bda-1fbbf781c397> Status: Connected Number of entries: 1 Brick arbiternode.domain.tld:/srv/glusterfs/myvolume/brick Status: Connected Number of entries: 0 On my node2 the respective .glusterfs/indices/xattrop directory contains two files as you can see below: ls -lai /data/myvolume/brick/.glusterfs/indices/xattrop total 76180 10 drw------- 2 root root 4 Jul 29 12:15 . 9 drw------- 5 root root 5 Apr 28 22:15 .. 2798404 ---------- 2 root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 2798404 ---...

To quickly resume my current situation: on node2 I have found the following file xattrop/indices file which matches the GFID of the "heal info" command (below is there output of "ls -lai": 2798404 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 As you can see this file has inode number 279840...

...hing appeared in that log file after running the above command. I checked the files which need to be healing using the "heal <volume> info" command and it still shows that very same GFID on node2 to be healed. So nothing changed here. The file /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 is only on node2 and not on my nod1 nor on my arbiternode. This file seems to be a regular file and not a symlink. Here is the output of the stat command on it from my node2: File: ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781...

...:/data/myvolume/brick > <gfid:29e0d13e-1217-41cc-9bda-1fbbf781c397> > Status: Connected > Number of entries: 1 > > Brick arbiternode.domain.tld:/srv/glusterfs/myvolume/brick > Status: Connected > Number of entries: 0 > > On my node2 the respective .glusterfs/indices/xattrop directory > contains two files as you can see below: > > ls -lai /data/myvolume/brick/.glusterfs/indices/xattrop > total 76180 > 10 drw------- 2 root root 4 Jul 29 12:15 . > 9 drw------- 5 root root 5 Apr 28 22:15 .. > 2798404 ---------- 2 root root 0 Apr 28 22:51...

On 07/31/2017 02:00 PM, mabi wrote: > To quickly resume my current situation: > > on node2 I have found the following file xattrop/indices file which > matches the GFID of the "heal info" command (below is there output of > "ls -lai": > > 2798404 ---------- 2 root root 0 Apr 28 22:51 > /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 > > > >...

...2017-06-19 17:42:35.339773495 +0200 Modify: 2017-06-19 17:42:35.343773437 +0200 Change: 2017-06-19 17:42:35.343773437 +0200 Birth: - What else can I do or try in order to fix this situation? > -------- Original Message -------- > Subject: Re: [Gluster-users] Possible stale .glusterfs/indices/xattrop file? > Local Time: July 31, 2017 3:27 AM > UTC Time: July 31, 2017 1:27 AM > From: ravishankar at redhat.com > To: mabi <mabi at protonmail.ch> > Gluster Users <gluster-users at gluster.org> > > On 07/30/2017 02:24 PM, mabi wrote: > >> Hi Ravi, >> Th...

...issing the hardlink inside .glusterfs folder since the link count is only 1. Thanks, Ravi > What else can I do or try in order to fix this situation? > > > > >> -------- Original Message -------- >> Subject: Re: [Gluster-users] Possible stale >> .glusterfs/indices/xattrop file? >> Local Time: July 31, 2017 3:27 AM >> UTC Time: July 31, 2017 1:27 AM >> From: ravishankar at redhat.com >> To: mabi <mabi at protonmail.ch> >> Gluster Users <gluster-users at gluster.org> >> >> >> >> >> On 07/30/2017 0...

...2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE arbiternode: find: '/data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397': No such file or directory Hope that helps. > -------- Original Message -------- > Subject: Re: [Gluster-users] Possible stale .glusterfs/indices/xattrop file? > Local Time: July 31, 2017 10:55 AM > UTC Time: July 31, 2017 8:55 AM > From: ravishankar at redhat.com > To: mabi <mabi at protonmail.ch> > Gluster Users <gluster-users at gluster.org> > > On 07/31/2017 02:00 PM, mabi wrote: > >> To quickly resume m...

...er running the above command. > I checked the files which need to be healing using the "heal <volume> > info" command and it still shows that very same GFID on node2 to be > healed. So nothing changed here. > > The file > /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 > is only on node2 and not on my nod1 nor on my arbiternode. This file > seems to be a regular file and not a symlink. Here is the output of > the stat command on it from my node2: > > File: > ?/data/myvolume/brick/.glusterfs/indices/xatt...

...glusterfs/blob/master/extras/gfid-to-dirname.sh Try to stat the file from a new (temporary) fuse mount to avoid any caching effects. -Ravi > > Hope that helps. > >> -------- Original Message -------- >> Subject: Re: [Gluster-users] Possible stale >> .glusterfs/indices/xattrop file? >> Local Time: July 31, 2017 10:55 AM >> UTC Time: July 31, 2017 8:55 AM >> From: ravishankar at redhat.com >> To: mabi <mabi at protonmail.ch> >> Gluster Users <gluster-users at gluster.org> >> >> >> >> >> On 07/31/2017...

...r issue (the thread was '[Gluster-users] glustershd: unable to get index-dir on myvolume-client-0'), the solution suggested was to verify if the /<path-to-backend-brick>/.glusterfs/indices directory contains all these sub directories: 'dirty', 'entry-changes' and 'xattrop' and if some of them does not exists simply create it with mkdir. In my case the 'entry-changes' directory is not present on all the bricks and on all the servers: /data/glusterfs/brick1a/hosted-engine/.glusterfs/indices/: total 0 drw------- 2 root root 55 Jun 28 15:02 dirty drw------...

...read was '[Gluster-users] glustershd: unable to get > index-dir on myvolume-client-0'), the solution suggested was to verify > if the /<path-to-backend-brick>/.glusterfs/indices directory contains > all these sub directories: 'dirty', 'entry-changes' and 'xattrop' and if > some of them does not exists simply create it with mkdir. > > In my case the 'entry-changes' directory is not present on all the > bricks and on all the servers: > > /data/glusterfs/brick1a/hosted-engine/.glusterfs/indices/: > total 0 > drw------- 2 roo...

in my /var/log/gluster/bricks/mybrick-path.log I get thousands of those errors: ------ [2017-11-22 21:06:23.768354] E [MSGID: 138003] [index.c:624:index_link_to_base] 0-sharedvol-index: /home/sharedvol/.glusterfs/indices/xattrop/0b852dad-b332-4bfe-a38b-976729ee46a2: Not able to add to index [Troppi collegamenti] The message "E [MSGID: 138003] [index.c:624:index_link_to_base] 0-sharedvol-index: /home/sharedvol/.glusterfs/indices/xattrop/0b852dad-b332-4bfe-a38b-976729ee46a2: Not able to add to index [Troppi collegamenti...

HI gluster experts, I meet a tough problem about ?split-brain? issue. Sometimes, after hard reboot, we will find some files in split-brain, however its parent directory or anything could be shown in command ?gluster volume heal <volume-name> info?, also, no entry in .glusterfs/indices/xattrop directory, can you help to shed some lights on this issue? Thanks! Following is some info from our env, Checking from sn-0 cliet, nothing is shown in-split-brain! [root at sn-0:/mnt/bricks/services/brick/netserv/ethip] # gluster v heal services info Brick sn-0:/mnt/bricks/services/brick/ Numbe...

...s, > > I meet a tough problem about ?split-brain? issue. Sometimes, after hard > reboot, we will find some files in split-brain, however its parent > directory or anything could be shown in command ?gluster volume heal > <volume-name> info?, also, no entry in .glusterfs/indices/xattrop > directory, can you help to shed some lights on this issue? Thanks! > > > > Following is some info from our env, > > *Checking from sn-0 cliet, nothing is shown in-split-brain!* > > [root at sn-0:/mnt/bricks/services/brick/netserv/ethip] > # gluster v heal services in...

...t;volume-name> info?. So these split-entry files could only be detected when app try to visit them. I can find gfid mismatch for those in-split-brain entries from mount log, however, nothing show in shd log, the shd log does not know those split-brain entries. Because there is nothing in indices/xattrop directory. The log is not available right now, when it reproduced, I will provide it to your, Thanks! Best regards, Cynthia ???? MBB SM HETRAN SW3 MATRIX Storage Mobile: +86 (0)18657188311 From: Karthik Subrahmanya [mailto:ksubrahm at redhat.com] Sent: Thursday, September 28, 2017 2:02 PM To: Zh...

...9;[Gluster-users] glustershd: unable to get >> index-dir on myvolume-client-0'), the solution suggested was to verify >> if the /<path-to-backend-brick>/.glusterfs/indices directory contains >> all these sub directories: 'dirty', 'entry-changes' and 'xattrop' and if >> some of them does not exists simply create it with mkdir. >> >> In my case the 'entry-changes' directory is not present on all the >> bricks and on all the servers: >> >> /data/glusterfs/brick1a/hosted-engine/.glusterfs/indices/: >> t...

...So these split-entry > files could only be detected when app try to visit them. > > I can find gfid mismatch for those in-split-brain entries from mount log, > however, nothing show in shd log, the shd log does not know those > split-brain entries. Because there is nothing in indices/xattrop directory. > I guess it was there before, and then it got cleared by one of the heal process either client side or server side. I wanted to check that by examining the logs. Which version of gluster you are running by the way? > > > The log is not available right now, when it reproduce...

...t;volume-name> info?. So these split-entry files could only be detected when app try to visit them. I can find gfid mismatch for those in-split-brain entries from mount log, however, nothing show in shd log, the shd log does not know those split-brain entries. Because there is nothing in indices/xattrop directory. I guess it was there before, and then it got cleared by one of the heal process either client side or server side. I wanted to check that by examining the logs. Which version of gluster you are running by the way? The log is not available right now, when it reproduced, I will provide it...

...yvolume-client-0'), the solution suggested was >> to verify >> if the /<path-to-backend-brick>/.glusterfs/indices directory >> contains >> all these sub directories: 'dirty', 'entry-changes' and >> 'xattrop' and if >> some of them does not exists simply create it with mkdir. >> >> In my case the 'entry-changes' directory is not present on >> all the >> bricks and on all the servers: >> >> /data/glusterfs/bric...