<div dir="ltr">The shared-brick-count value indicates the number of bricks sharing a file-system. In your case, it should be one, as all the bricks are from different mount points. Can you please share the values of brick-fsid?<div><br></div><div>grep &quot;brick-fsid&quot; /var/lib/glusterd/vols/&lt;volname&gt;/bricks/</div><div><br></div><div>I tried reproducing this issue in fedora vm&#39;s but couldn&#39;t hit this. we are seeing this issue on and off but are unable to reproduce in-house. If you see any error messages in glusterd.log please share the log too.</div><div><br></div><div>Work-around to come out from this situation:</div><div>1. Restarting the glusterd service on all nodes:<br># systemctl restart glusterd<br><br>2. Run set volume command to update vol file:<br># gluster v set &lt;VOLNAME&gt; <span class="gmail-il">min</span>-<span class="gmail-il">free</span>-<span class="gmail-il">disk</span> 11%<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 27, 2020 at 5:24 PM Petr Certik &lt;<a href="mailto:petr@certik.cz">petr@certik.cz</a>&gt; 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">As far as I remember, there was no version update on the server. It<br>
was definitely installed as version 7.<br>
<br>
Shared bricks:<br>
<br>
Server 1:<br>
<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster1.data2-brick.vol:<br>
option shared-brick-count 2<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster1.data-brick.vol:    option<br>
shared-brick-count 2<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster2.data2-brick.vol:<br>
option shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster2.data-brick.vol:    option<br>
shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster3.data2-brick.vol:<br>
option shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster3.data-brick.vol:    option<br>
shared-brick-count 0<br>
<br>
Server 2:<br>
<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster1.data2-brick.vol:<br>
option shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster1.data-brick.vol:    option<br>
shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster2.data2-brick.vol:<br>
option shared-brick-count 2<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster2.data-brick.vol:    option<br>
shared-brick-count 2<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster3.data2-brick.vol:<br>
option shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster3.data-brick.vol:    option<br>
shared-brick-count 0<br>
<br>
Server 3:<br>
<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster1.data2-brick.vol:<br>
option shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster1.data-brick.vol:    option<br>
shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster2.data2-brick.vol:<br>
option shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster2.data-brick.vol:    option<br>
shared-brick-count 0<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster3.data2-brick.vol:<br>
option shared-brick-count 2<br>
/var/lib/glusterd/vols/gv0/gv0.imagegluster3.data-brick.vol:    option<br>
shared-brick-count 2<br>
<br>
On Wed, May 27, 2020 at 1:36 PM Sanju Rakonde &lt;<a href="mailto:srakonde@redhat.com" target="_blank">srakonde@redhat.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Petr,<br>
&gt;<br>
&gt; what was the server version before upgrading to 7.2?<br>
&gt;<br>
&gt; Can you please share the shared-brick-count values from brick volfiles from all the nodes?<br>
&gt; grep shared-brick-count /var/lib/glusterd/vols/&lt;volume_name&gt;/*<br>
&gt;<br>
&gt; On Wed, May 27, 2020 at 2:31 PM Petr Certik &lt;<a href="mailto:petr@certik.cz" target="_blank">petr@certik.cz</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi everyone,<br>
&gt;&gt;<br>
&gt;&gt; we&#39;ve been running a replicated volume for a while, with three ~1 TB<br>
&gt;&gt; bricks. Recently we&#39;ve added three more same-sized bricks, making it a<br>
&gt;&gt; 2 x 3 distributed replicated volume. However, even after rebalance,<br>
&gt;&gt; the `df` command on a client shows the correct used/size percentage,<br>
&gt;&gt; but wrong absolute sizes. The size still shows up as ~1 TB while in<br>
&gt;&gt; reality it should be around 2 TB, and both &quot;used&quot; and &quot;available&quot;<br>
&gt;&gt; reported sizes are about half of what they should be. The clients were<br>
&gt;&gt; an old version (5.5), but even after upgrade to 7.2 and remount, the<br>
&gt;&gt; reported sizes are still wrong. There are no heal entries. What can I<br>
&gt;&gt; do to fix this?<br>
&gt;&gt;<br>
&gt;&gt; OS: debian buster everywhere<br>
&gt;&gt; Server version: 7.3-1, opversion: 70200<br>
&gt;&gt; Client versions: 5.5-3, 7.6-1, opversions: 50400, 70200<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; root@imagegluster1:~# gluster volume info gv0<br>
&gt;&gt; Volume Name: gv0<br>
&gt;&gt; Type: Distributed-Replicate<br>
&gt;&gt; Volume ID: 5505d350-9b61-4056-9054-de9dfb58eab7<br>
&gt;&gt; Status: Started<br>
&gt;&gt; Snapshot Count: 0<br>
&gt;&gt; Number of Bricks: 2 x 3 = 6<br>
&gt;&gt; Transport-type: tcp<br>
&gt;&gt; Bricks:<br>
&gt;&gt; Brick1: imagegluster1:/data/brick<br>
&gt;&gt; Brick2: imagegluster2:/data/brick<br>
&gt;&gt; Brick3: imagegluster3:/data/brick<br>
&gt;&gt; Brick4: imagegluster1:/data2/brick<br>
&gt;&gt; Brick5: imagegluster2:/data2/brick<br>
&gt;&gt; Brick6: imagegluster3:/data2/brick<br>
&gt;&gt; Options Reconfigured:<br>
&gt;&gt; features.cache-invalidation: on<br>
&gt;&gt; transport.address-family: inet<br>
&gt;&gt; storage.fips-mode-rchecksum: on<br>
&gt;&gt; nfs.disable: on<br>
&gt;&gt; performance.client-io-threads: off<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; root@imagegluster1:~# df -h<br>
&gt;&gt; Filesystem      Size  Used Avail Use% Mounted on<br>
&gt;&gt; ...<br>
&gt;&gt; /dev/sdb1       894G  470G  425G  53% /data2<br>
&gt;&gt; /dev/sdc1       894G  469G  426G  53% /data<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; root@any-of-the-clients:~# df -h<br>
&gt;&gt; Filesystem         Size  Used Avail Use% Mounted on<br>
&gt;&gt; ...<br>
&gt;&gt; imagegluster:/gv0  894G  478G  416G  54% /mnt/gluster<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Let me know if there&#39;s any other info I can provide about our setup.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt; Petr Certik<br>
&gt;&gt; ________<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Community Meeting Calendar:<br>
&gt;&gt;<br>
&gt;&gt; Schedule -<br>
&gt;&gt; Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
&gt;&gt; Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
&gt;&gt;<br>
&gt;&gt; Gluster-users mailing list<br>
&gt;&gt; <a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
&gt;&gt; <a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Thanks,<br>
&gt; Sanju<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div>Thanks,<br></div>Sanju<br></div></div>