<div dir="ltr"><div>Yes you can directly update the volfile and restart the glusterd.</div><div>Please file a github issue if you are facing any issue further.</div><div><br></div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 19, 2022 at 5:32 PM <<a href="mailto:gluster-users-request@gluster.org">gluster-users-request@gluster.org</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">Send Gluster-users mailing list submissions to<br>
<a href="mailto:gluster-users@gluster.org" target="_blank">gluster-users@gluster.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<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>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:gluster-users-request@gluster.org" target="_blank">gluster-users-request@gluster.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:gluster-users-owner@gluster.org" target="_blank">gluster-users-owner@gluster.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Gluster-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Mounted size reported incorrectly after replacing bricks<br>
(Patrick Dijkgraaf)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 19 Apr 2022 11:30:05 +0200<br>
From: Patrick Dijkgraaf <<a href="mailto:bolderbasta@gmail.com" target="_blank">bolderbasta@gmail.com</a>><br>
To: <a href="mailto:gluster-users@gluster.org" target="_blank">gluster-users@gluster.org</a><br>
Subject: [Gluster-users] Mounted size reported incorrectly after<br>
replacing bricks<br>
Message-ID: <<a href="mailto:da1e295b001824362e4dab0180ce41859f7c9bf3.camel@gmail.com" target="_blank">da1e295b001824362e4dab0180ce41859f7c9bf3.camel@gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi all, I hope this message finds you well.<br>
<br>
I sent some messages earlier, but I found that they bounced a lot due<br>
to DMARC/SPF, so I am sending this question again from another mail<br>
account. Please accept my apologies for spamming.<br>
<br>
I've been running a Gluster volume (32 bricks in distributed,<br>
replicated mode) on my 2 home servers for about 1,5 years now. I'm<br>
generally very happy with it!<br>
It's running on Arch Linux and the current version of glusterfs is<br>
10.1.<br>
<br>
Because some disks were about to fail, I started replacing multiple<br>
bricks. And taking advantage of this, I replaced them with a larger<br>
disk (4TB -> 8TB). Healing took care of copying all data to the new<br>
brick and it finished succesfully. However, I see an incorrect size on<br>
the mounted Gluster volume.<br>
<br>
Some things I have found:<br>
<br>
* shared-brick-count in /var/lib/glusterd/vols/data/* is higher than 1<br>
on some local bricks, even though they are actually on separate file<br>
systems<br>
* I have duplicate brick-fsid numbers in<br>
/var/lib/glusterd/vols/data/bricks/*, even though they are actually<br>
on separate file systems<br>
* I have restarted glusterd and still have the duplicate brick-fsid's<br>
<br>
So I am wondering where the duplicate FSIDs come from, and how to<br>
(forcefully?) resolve them. Can I safely alter them in<br>
/var/lib/glusterd/vols/data/bricks/* and restart glusterd maybe?<br>
<br>
I *may* at some point have accidentally replaced a brick to a wrong<br>
location, being either the parent file system or another brick. But I<br>
have corrected this by replacing it again to the correct location. Each<br>
time I used the "gluster volume replace-brick" command.<br>
<br>
I have attached what I believe would be all relevant information to<br>
diagnose the issue.<br>
Please let me know if I can provide more information to get this issue<br>
resolved.<br>
<br>
-- <br>
groet / cheers,<br>
Patrick Dijkgraaf<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.gluster.org/pipermail/gluster-users/attachments/20220419/40df9490/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.gluster.org/pipermail/gluster-users/attachments/20220419/40df9490/attachment-0001.html</a>><br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: Gluster issue.zip<br>
Type: application/zip<br>
Size: 211469 bytes<br>
Desc: not available<br>
URL: <<a href="http://lists.gluster.org/pipermail/gluster-users/attachments/20220419/40df9490/attachment-0001.zip" rel="noreferrer" target="_blank">http://lists.gluster.org/pipermail/gluster-users/attachments/20220419/40df9490/attachment-0001.zip</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<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>
------------------------------<br>
<br>
End of Gluster-users Digest, Vol 168, Issue 13<br>
**********************************************<br>
<br>
</blockquote></div></div>