<div dir="ltr">Hi,<div><br></div><div>I am assuming that you are using one of the maintained versions of gluster.</div><div><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px">GFID split-brains can be resolved using one of the methods in the split-brain resolution CLI as explained in the section "3. Resolution of split-brain using gluster CLI" of <a rel="nofollow" href="https://docs.gluster.org/en/latest/Troubleshooting/resolving-splitbrain/" style="box-sizing:border-box;background-color:initial;color:rgb(3,102,214);text-decoration-line:none">https://docs.gluster.org/en/latest/Troubleshooting/resolving-splitbrain/</a>.</p><p style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji";font-size:14px">The things to be noted here while using this CLI for resolving gfid split-brains are:<br style="box-sizing:border-box">- You can not use the GFID of the file as an argument with any of the CLI options to resolve GFID split-brain. It should be the absolute path as seen from the mount point to the file considered as source.<br style="box-sizing:border-box">- With source-brick option there is no way to resolve all the GFID split-brain in one shot by not specifying any file-path in the CLI as done while resolving data or metadata split-brain. For each file in GFID split-brain, run the CLI with the policy you want to use.<br style="box-sizing:border-box">- Resolving directory GFID split-brain using CLI with the "source-brick" option in a "distributed-replicated" volume needs to be done on all the volumes explicitly if the file is in gfid split-brain on multiple subvolumes. Since directories get created on all the subvolumes, using one particular brick as source for directory GFID split-brain, heal the directories for that subvolume. In this case, other subvolumes must be healed using the brick which has the same GFID as that of the previous brick which was used as source for healing other subvolume.</p>Regards,<br>Karthik</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, May 30, 2020 at 3:39 AM lejeczek <<a href="mailto:peljasz@yahoo.co.uk">peljasz@yahoo.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hi Guys<br>
<br>
I'm seeing "Gfid mismatch detected" in the logs but no split<br>
brain indicated (4-way replica)<br>
<br>
Brick<br>
swir-ring8:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER.USER-HOME<br>
Status: Connected<br>
Total Number of entries: 22<br>
Number of entries in heal pending: 22<br>
Number of entries in split-brain: 0<br>
Number of entries possibly healing: 0<br>
<br>
Brick<br>
whale-ring8:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER.USER-HOME<br>
Status: Connected<br>
Total Number of entries: 22<br>
Number of entries in heal pending: 22<br>
Number of entries in split-brain: 0<br>
Number of entries possibly healing: 0<br>
<br>
Brick<br>
rider-ring8:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER.USER-HOME<br>
Status: Connected<br>
Total Number of entries: 0<br>
Number of entries in heal pending: 0<br>
Number of entries in split-brain: 0<br>
Number of entries possibly healing: 0<br>
<br>
Brick dzien:/__.aLocalStorages/0/0-GLUSTERs/0GLUSTER.USER-HOME<br>
Status: Connected<br>
Total Number of entries: 10<br>
Number of entries in heal pending: 10<br>
Number of entries in split-brain: 0<br>
Number of entries possibly healing: 0<br>
<br>
On swir-ring8:<br>
...<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:bea05f85-a20e-4cbf-9e41-5e351f99b396>/lock_file>,<br>
37b2456f-5216-4679-ac5c-4908b24f895a on USER-HOME-client-15<br>
and ba8f87ed-9bf3-404e-8d67-2631923e1645 on<br>
USER-HOME-client-13." repeated 2 times between [2020-05-29<br>
21:47:49.034935] and [2020-05-29 21:47:49.079480]<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:a8a084b9-6484-48be-bec7-e704cf5ab880>/t>,<br>
d7a4ed01-139b-4df3-8070-31bd620a6f15 on USER-HOME-client-15<br>
and d794b6ba-2a1d-4043-bb31-b98b22692763 on<br>
USER-HOME-client-13." repeated 2 times between [2020-05-29<br>
21:47:49.126173] and [2020-05-29 21:47:49.155432]<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:1f686fba-e325-4539-bf48-94b06325d2f4>/Tables.docx>,<br>
344febd8-c89c-4bf3-8ad8-6494c2189c43 on USER-HOME-client-15<br>
and 48d5b12b-03f4-46bf-bed1-9f8f88815615 on<br>
USER-HOME-client-13." repeated 2 times between [2020-05-29<br>
21:47:49.194061] and [2020-05-29 21:47:49.239896]<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-entry.c:257:afr_selfheal_detect_gfid_and_type_mismatch]<br>
0-USER-HOME-replicate-0: Skipping conservative merge on the<br>
file." repeated 8 times between [2020-05-29 21:47:49.037812]<br>
and [2020-05-29 21:47:49.240423]<br>
...<br>
<br>
On whale-ring8:<br>
...<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:e57771ac-c18d-44fe-81ff-6e9072d9c9ef>/pcs>,<br>
a83d0e5f-ef3a-40ab-be7b-784538d150be on USER-HOME-client-15<br>
and 89af3d31-81fa-4242-b8f7-0f49fd5fe57b on<br>
USER-HOME-client-13." repeated 2 times between [2020-05-29<br>
21:45:46.152052] and [2020-05-29 21:45:46.422393]<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:e57771ac-c18d-44fe-81ff-6e9072d9c9ef>/history_database>,<br>
81ebb0d5-264a-4eba-984a-e18673b43826 on USER-HOME-client-15<br>
and 2498a303-8937-43c3-939e-5e1d786b07fa on<br>
USER-HOME-client-13." repeated 2 times between [2020-05-29<br>
21:45:46.167704] and [2020-05-29 21:45:46.437702]<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:e57771ac-c18d-44fe-81ff-6e9072d9c9ef>/client-state>,<br>
fe86c057-c74d-417f-9c2c-6e6eb9778851 on USER-HOME-client-15<br>
and a66f2714-c2a0-4bdc-8786-ad5b93e0e988 on<br>
USER-HOME-client-13." repeated 2 times between [2020-05-29<br>
21:45:46.144242] and [2020-05-29 21:45:46.442526]<br>
The message "E [MSGID: 108008]<br>
[afr-self-heal-common.c:384:afr_gfid_split_brain_source]<br>
0-USER-HOME-replicate-0: Gfid mismatch detected for<br>
<gfid:e57771ac-c18d-44fe-81ff-6e9072d9c9ef>/history_database.1>,<br>
9826d8ad-fecc-4dd7-bc1f-87d0eff23d73 on USER-HOME-client-15<br>
and 81ebb0d5-264a-4eba-984a-e18673b43826 on<br>
USER-HOME-client-13." repeated 3 times between [2020-05-29<br>
21:45:46.162016] and [2020-05-29 21:45:46.476935]<br>
...<br>
<br>
On rider-ring8:<br>
...<br>
2020-05-29 21:46:53.122929] E [MSGID: 114031]<br>
[client-rpc-fops_v2.c:1548:client4_0_xattrop_cbk]<br>
0-QEMU_VMs-client-3: remote operation failed. Path:<br>
<gfid:6f01098f-e8db-4f63-a661-86b4d02d937f><br>
(6f01098f-e8db-4f63-a661-86b4d02d937f) [Permission denied]<br>
[2020-05-29 21:46:53.124148] E [MSGID: 114031]<br>
[client-rpc-fops_v2.c:1548:client4_0_xattrop_cbk]<br>
0-QEMU_VMs-client-4: remote operation failed. Path:<br>
<gfid:6f01098f-e8db-4f63-a661-86b4d02d937f><br>
(6f01098f-e8db-4f63-a661-86b4d02d937f) [Permission denied]<br>
[2020-05-29 21:46:53.133566] I [MSGID: 108026]<br>
[afr-self-heal-entry.c:898:afr_selfheal_entry_do]<br>
0-QEMU_VMs-replicate-0: performing entry selfheal on<br>
e0121f76-2452-44dc-b1a6-82b46cc9ec79<br>
[2020-05-29 21:46:53.145991] E [MSGID: 114031]<br>
[client-rpc-fops_v2.c:1548:client4_0_xattrop_cbk]<br>
0-QEMU_VMs-client-3: remote operation failed. Path:<br>
<gfid:3f0239ac-e027-4a0c-b271-431e76ad97b1><br>
(3f0239ac-e027-4a0c-b271-431e76ad97b1) [Permission denied]<br>
[2020-05-29 21:46:53.147110] E [MSGID: 114031]<br>
[client-rpc-fops_v2.c:1548:client4_0_xattrop_cbk]<br>
0-QEMU_VMs-client-4: remote operation failed. Path:<br>
<gfid:3f0239ac-e027-4a0c-b271-431e76ad97b1><br>
(3f0239ac-e027-4a0c-b271-431e76ad97b1) [Permission denied]<br>
<br>
The most recent data I'm 100% certain is on rider-ring8.<br>
Any expert could probably quickly suggest how to go about<br>
the problem.<br>
Would something like manual healing with 'source-brick' or<br>
'latest-mtime' work or is too naive?<br>
<br>
many thanks, L.<br>
<br>
<br>
________<br>
<br>
<br>
<br>
Community Meeting Calendar:<br>
<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
</blockquote></div>