search for: arbiternode

Do you see any session listed when Geo-replication status command is run(without any volume name) gluster volume geo-replication status Volume stop force should work even if Geo-replication session exists. From the error it looks like node "arbiternode.domain.tld" in Master cluster is down or not reachable. regards Aravinda VK On 08/07/2017 10:01 PM, mabi wrote: > Hi, > > I would really like to get rid of this geo-replication session as I am > stuck with it right now. For example I can't even stop my volume as it > co...

When I run the "gluster volume geo-replication status" I see my geo replication session correctly including the volume name under the "VOL" column. I see my two nodes (node1 and node2) but not arbiternode as I have added it later after setting up geo-replication. For more details have a quick look at my previous post here: http://lists.gluster.org/pipermail/gluster-users/2017-July/031911.html Sorry for repeating myself but again: how can I manually delete this problematic geo-replication session? It...

...would like to delete a geo-replication session on my GluterFS 3.8.11 replicat 2 volume in order to re-create it. Unfortunately the "delete" command does not work as you can see below: $ sudo gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-geo delete Staging failed on arbiternode.domain.tld. Error: Geo-replication session between myvolume and arbiternode.domain.tld::myvolume-geo does not exist. geo-replication command failed I also tried with "force" but no luck here either: $ sudo gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-geo delete for...

Hi Ji-Hyeon, Thanks to your help I could find out the problematic file. This would be the quota file of my volume it has a different checksum on node1 whereas node2 and arbiternode have the same checksum. This is expected as I had issues which my quota file and had to fix it manually with a script (more details on this mailing list in a previous post) and I only did that on node1. So what I now did is to copy /var/lib/glusterd/vols/myvolume/quota.conf file from node1 to node2...

...lication/). regards Aravinda VK On 08/08/2017 12:08 PM, mabi wrote: > When I run the "gluster volume geo-replication status" I see my geo > replication session correctly including the volume name under the > "VOL" column. I see my two nodes (node1 and node2) but not arbiternode > as I have added it later after setting up geo-replication. For more > details have a quick look at my previous post here: > > http://lists.gluster.org/pipermail/gluster-users/2017-July/031911.html > > Sorry for repeating myself but again: how can I manually delete this > p...

...lled the glusterd and glusterfs process. I restarted the glusterd process but now that node is in "Peer Rejected" state from the other nodes and from itself it rejects the two other nodes as you can see below from the output of "gluster peer status": Number of Peers: 2 Hostname: arbiternode.domain.tld Uuid: 60a03a81-ba92-4b84-90fe-7b6e35a10975 State: Peer Rejected (Connected) Hostname: node2.domain.tld Uuid: 4834dceb-4356-4efb-ad8d-8baba44b967c State: Peer Rejected (Connected) I also rebooted my node1 just in case but that did not help. I read here http://www.spinics.net/lists/gluster...

...e to delete a geo-replication session on my GluterFS 3.8.11 replicat 2 volume in order to re-create it. Unfortunately the "delete" command does not work as you can see below: > $ sudo gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-geo delete > Staging failed on arbiternode.domain.tld. Error: Geo-replication session between myvolume and arbiternode.domain.tld::myvolume-geo does not exist. > geo-replication command failed > I also tried with "force" but no luck here either: > $ sudo gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume...

...cess. I restarted the glusterd process but > now that node is in "Peer Rejected" state from the other nodes and > from itself it rejects the two other nodes as you can see below from > the output of "gluster peer status": > > Number of Peers: 2 > > Hostname: arbiternode.domain.tld > Uuid: 60a03a81-ba92-4b84-90fe-7b6e35a10975 > State: Peer Rejected (Connected) > > Hostname: node2.domain.tld > Uuid: 4834dceb-4356-4efb-ad8d-8baba44b967c > State: Peer Rejected (Connected) > > > > I also rebooted my node1 just in case but that did not help...

...mmand (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 2798404, so I ran the following command on all my nodes (node1, node2 and arbiternode): sudo find /data/myvolume/brick -inum 2798404 -ls Here below are the results for all 3 nodes: node1: 2798404 19 -rw-r--r-- 2 www-data www-data 32 Jun 19 17:42 /data/myvolume/brick/.glusterfs/e6/5b/e65b77e2-a4c4-4824-a7bb-58df969ce4b0 2798404 19 -rw-r--r-- 2 www-data www-data 32 Jun 19 17:42 /data/...

...41cc-9bda-1fbbf781c397 -> ../../fe/c0/fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE node2: 8394638 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43 /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397 -> ../../fe/c0/fec0e4f4-38d2-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...

I did a find on this inode number and I could find the file but only on node1 (nothing on node2 and the new arbiternode). Here is an ls -lai of the file itself on node1: -rw-r--r-- 1 www-data www-data 32 Jun 19 17:42 fileKey As you can see it is a 32 bytes file and as you suggested I ran a "stat" on this very same file through a glusterfs mount (using fuse) but unfortunately nothing happened. The GFID is s...

...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 2798404, so I ran the > following command on all my nodes (node1, node2 and arbiternode): ...which is what I was saying is incorrect. 2798404 is an XFS inode number and is not common to the same file across nodes. So you will get different results. Use the -samefile flag I shared earlier. -Ravi > > sudo find /data/myvolume/brick -inum 2798404 -ls > > Here below are th...

...atus "Faulty" and keeps trying over and over to sync without success. I am using GlusterFS 3.8.11. So in order to stop geo-rep I use: gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-geo stop but it fails to stop it as you can see in the output below: Staging failed on arbiternode.domain.tld. Error: Geo-replication session between myvolume and gfs1geo.domain.tld::myvolume-geo does not exist. geo-replication command failed How can I now stop geo replication? Is there a manual way to do that? Regards, Mabi -------------- next part -------------- An HTML attachment was scrubbed...

...dc0b9b54810/OC_DEFAULT_MODULE > > node2: > 8394638 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43 > /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397 > -> ../../fe/c0/fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE > > > > arbiternode: > find: > '/data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397': > No such file or directory Right, so the file OC_DEFAULT_MODULE is missing in this brick It's parent directory has gfid fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810. Goal is to do a stat of t...

On 07/31/2017 12:20 PM, mabi wrote: > I did a find on this inode number and I could find the file but only > on node1 (nothing on node2 and the new arbiternode). Here is an ls > -lai of the file itself on node1: Sorry I don't understand, isn't that (XFS) inode number specific to node2's brick? If you want to use the same command, maybe you should try `find /data/myvolume/brick -samefile /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-121...

...eed 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-1fbbf781c397? Size: 0 Blocks: 1 IO Block: 512 regular empty file Device: 25h/37d Inode: 2798404 Links:...

...but there are still other issues related to the fact that my geo replication setup was created before I added the additional arbiter node to my replca. For example when I would like to stop my volume I simply can't and I get the following error: volume stop: myvolume: failed: Staging failed on arbiternode.domain.tld. Error: geo-replication Unable to get the status of active geo-replication session for the volume 'myvolume'. What should I do here? Should I delete the geo-replication and re-create it? Will it then have to sync again all my data? I have around 500 GB of data so I would like to...

...nc > without success. I am using GlusterFS 3.8.11. > > So in order to stop geo-rep I use: > > gluster volume geo-replication myvolume gfs1geo.domain.tld::myvolume-geo > stop > > > > but it fails to stop it as you can see in the output below: > > Staging failed on arbiternode.domain.tld. Error: Geo-replication session > between myvolume and gfs1geo.domain.tld::myvolume-geo does not exist. > geo-replication command failed > > How can I now stop geo replication? Is there a manual way to do that? > > Regards, > Mabi > > __________________________...

...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-1fbbf781c397? > Size: 0 Blocks: 1 IO Block: 512...

...ot get healed as you can see here from the output of a "heal info": Brick node1.domain.tld:/data/myvolume/brick Status: Connected 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 d...