search for: 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 2798404, so I ran the following command on all my nodes (node1, node2 and arbiternode): sudo find /data/myvolume/brick -inum 2798404 -...

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 > > > > 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...

...ster.org> > > 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 >> 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 sayi...

...t;>> 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 2798404, so I ran the >>> following command on all my node...

...gt;> 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: 2 >> >> Okay, link count of 2 means there is a hardlink somewhere on the >> brick. Try the find command again. I see that the inode number is >> 2798404, not the one you shared in your first mail. Once you find the >> path to the file, do a stat of the fi...

...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: 2 > > Okay, link count of 2 means there is a hardlink somewhere on the brick. Try the find command again. I see that the inode number is 2798404, not the one you shared in your first mail. Once you find the path to the file, do a stat of the file from mount. This should create the entr...

...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: 2 Access: (0000/----------) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2017-04-28 22:51:15.215775269 +0200 Modify: 2017-04-28 22:51:15.215775269 +0200 Change: 2017-07-30 08:39:03.700872312 +0200 Birth: - I hope this is enough info for a starter, else let me know if you need any more info. I wou...

...k 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 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/bric...

...d 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: 2 Okay, link count of 2 means there is a hardlink somewhere on the brick. Try the find command again. I see that the inode number is 2798404, not the one you shared in your first mail. Once you find the path to the file, do a stat of the file from mount. This should create the entry...

...ode2 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 ---------- 2 root root 0 Apr 28 22:51 > xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 > > > > I tried to find the real file on my brick where this xattrop file > points to using its inod...