<div dir="ltr">Hi Guys,<div><br></div><div>I pushed some VMs to the GlusterFS storage this week and ran them there. For a maintenance task, I moved these VMs to Proxmox-Node-2 and took Node-1 offline for a short time.</div><div>After moving them back to Node-1 there were some file corpses left (see attachment). In the logs I can't find anything about the gfids :)<br></div><div><br></div><div><br></div><div>┬[15:36:51] [ssh:root@pve02(192.168.1.51): /home/darkiop (755)]<br>╰─># gvi<br><br>Cluster:<br> Status: Healthy GlusterFS: 9.3<br> Nodes: 3/3 Volumes: 1/1<br><br>Volumes: <br><br>glusterfs-1-volume<br> Replicate Started (UP) - 3/3 Bricks Up - (Arbiter Volume)<br> Capacity: (17.89% used) 83.00 GiB/466.00 GiB (used/total)<br> Self-Heal:<br> 192.168.1.51:/data/glusterfs (4 File(s) to heal).<br> Bricks:<br> Distribute Group 1:<br> 192.168.1.50:/data/glusterfs (Online)<br> 192.168.1.51:/data/glusterfs (Online)<br> 192.168.1.40:/data/glusterfs (Online)<br><br><br>Brick 192.168.1.50:/data/glusterfs<br>Status: Connected<br>Number of entries: 0<br><br>Brick 192.168.1.51:/data/glusterfs<br><gfid:ade6f31c-b80b-457e-a054-6ca1548d9cd3> <br><gfid:39365c96-296b-4270-9cdb-1b751e40ad86> <br><gfid:54774d44-26a7-4954-a657-6e4fa79f2b97> <br><gfid:d5a8ae04-7301-4876-8d32-37fcd6093977> <br>Status: Connected<br>Number of entries: 4<br><br>Brick 192.168.1.40:/data/glusterfs<br>Status: Connected<br>Number of entries: 0<br><br><br>┬[15:37:03] [ssh:root@pve02(192.168.1.51): /home/darkiop (755)]<br>╰─># cat /data/glusterfs/.glusterfs/ad/e6/ade6f31c-b80b-457e-a054-6ca1548d9cd3<br>22962<br><br><br>┬[15:37:13] [ssh:root@pve02(192.168.1.51): /home/darkiop (755)]<br>╰─># grep -ir 'ade6f31c-b80b-457e-a054-6ca1548d9cd3' /var/log/glusterfs/*.log<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Mo., 1. Nov. 2021 um 07:51 Uhr schrieb Thorsten Walk <<a href="mailto:darkiop@gmail.com" target="_blank">darkiop@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>After deleting the file, output of heal info is clear.</div><div><br></div>>Not sure why you ended up in this situation (maybe unlink partially failed on this brick?)<div><br></div><div>Neither did I, this was a completely fresh setup with 1-2 VMs and 1-2 Proxmox LXC templates. I let it run for a few days and at some point it had the mentioned state. I continue to monitor and start with fill the bricks with data.<br>Thanks for your help!<br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Mo., 1. Nov. 2021 um 02:54 Uhr schrieb Ravishankar N <<a href="mailto:ravishankar.n@pavilion.io" target="_blank">ravishankar.n@pavilion.io</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 1, 2021 at 12:02 AM Thorsten Walk <<a href="mailto:darkiop@gmail.com" target="_blank">darkiop@gmail.com</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"><div dir="ltr"><div dir="ltr">Hi Ravi, the file only exists at pve01 and since only once:<div><br></div><div>┬[19:22:10] [ssh:root@pve01(192.168.1.50): ~ (700)]<br>╰─># stat /data/glusterfs/.glusterfs/26/c5/26c5396c-86ff-408d-9cda-106acd2b0768<br> File: /data/glusterfs/.glusterfs/26/c5/26c5396c-86ff-408d-9cda-106acd2b0768<br> Size: 6 Blocks: 8 IO Block: 4096 regular file<br>Device: fd12h/64786d Inode: 528 Links: 1<br>Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)<br>Access: 2021-10-30 14:34:50.385893588 +0200<br>Modify: 2021-10-27 00:26:43.988756557 +0200<br>Change: 2021-10-27 00:26:43.988756557 +0200<br> Birth: -<br></div></div><div><br></div><div>┬[19:24:41] [ssh:root@pve01(192.168.1.50): ~ (700)]<br>╰─># ls -l /data/glusterfs/.glusterfs/26/c5/26c5396c-86ff-408d-9cda-106acd2b0768<br>.rw-r--r-- root root 6B 4 days ago /data/glusterfs/.glusterfs/26/c5/26c5396c-86ff-408d-9cda-106acd2b0768<br><br>┬[19:24:54] [ssh:root@pve01(192.168.1.50): ~ (700)]<br>╰─># cat /data/glusterfs/.glusterfs/26/c5/26c5396c-86ff-408d-9cda-106acd2b0768<br>28084<br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr"><br></div></div></div></blockquote><div>Hi Thorsten, you can delete the file. From the file size and contents, it looks like it belongs to ovirt sanlock. Not sure why you ended up in this situation (maybe unlink partially failed on this brick?). You can check the mount, brick and self-heal daemon logs for this gfid to see if you find related error/warning messages.</div><div><br></div><div>-Ravi</div></div></div>
</blockquote></div></div></div>
</blockquote></div>