On February 1, 2020 10:53:59 AM GMT+02:00, Christian Reiss <email@christian-reiss.de> wrote:
Hey Strahil,
thanks for your answer.
On 01/02/2020 08:18, Strahil Nikolov wrote:
There is an active thread in gluster-users , so it will be nice to mention this there.
About the sync, you can find the paths via: 1. Mount mount -t glusterfs -o aux-gfid-mount vm1:test /mnt/testvol 2. Find the path of files: getfattr -n trusted.glusterfs.pathinfo -e text/mnt/testvol/.gfid/<GFID>
I bet it's the same file that causes me problems. Just verify the contents and you will see that one of them is newer -> just rsync it to the bricks node01 & node03 and run 'gluster volume heal <volume> full.'
I did a cross-post to gluster-users just now. You are right, the brick-files have a slightly different timestamp:
[root@node01:~] # stat /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 File: ‘/gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6’ Size: 67108864 Blocks: 54576 IO Block: 4096 regular file Device: fd09h/64777d Inode: 16152829909 Links: 2 Access: (0660/-rw-rw----) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:glusterd_brick_t:s0 Access: 2020-01-31 22:16:57.812620635 +0100 Modify: 2020-02-01 07:19:24.183045141 +0100 Change: 2020-02-01 07:19:24.186045203 +0100 Birth: -
[root@node03:~] # stat /gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6 File: ‘/gluster_bricks/ssd_storage/ssd_storage/.glusterfs/a1/21/a121e4fb-0984-4e41-94d7-8f0c4f87f4b6’ Size: 67108864 Blocks: 54576 IO Block: 4096 regular file Device: fd09h/64777d Inode: 16154259424 Links: 2 Access: (0660/-rw-rw----) Uid: ( 0/ root) Gid: ( 0/ root) Context: system_u:object_r:glusterd_brick_t:s0 Access: 2020-01-31 22:16:57.811800217 +0100 Modify: 2020-02-01 07:19:24.180939487 +0100 Change: 2020-02-01 07:19:24.184939586 +0100 Birth: -
Contents (getfattr, md5) are still identical.
I am unsure about your suggested rsync, tho:
- node1 has file, - node2 does not, - node3 has file.
So I can rsync node1 to node2 and node3 or node3 to node1 and node2. Sync to node1 and node3 cant be done as node2 does not have the file.
Can I do the rsync on a live, running Gluster?
Hm .. Just copy the file to node2 as it is missing. In my case ovirt2 had a newer file than 1 & 3 Yes, you can sync the files - just place them in the same folder. Best Regards, Strahil Nikolov