[Gluster-devel] Expanding Volume problem in old release 3.12.2

[PSC]

Hello, 
we did more test, after we do rebalance, those old files will move to new bricks, but for files newly write to volume, they will still go to old bricks.
However, once the server which added bricks had been restart. Everything works correctly, new files write to volume will also go to new bricks.
Is there anything we missed? 


we add bricks with:
# gluster volume add-brick VOLNAME NEW_BRICK


rebalance it with:
# gluster volume rebalance <VOLNAME> fix-layout start 


But it is not work properly until we restart the machine.


------------------ Original ------------------
From:  "PSC";<1173701037 at qq.com>;
Date:  Dec 30, 2019
To:  "Amar Tumballi"<amarts at gmail.com>; 
Cc:  "gluster-devel"<gluster-devel at gluster.org>; 
Subject:  Re:  [Gluster-devel] Expanding Volume problem in old release 3.12.2





Thank you for your reply,
Yes we did, once we do the rebalance process, those files already on old bricks will move to new bricks. However, if we write new files to volume, they will still distributed to old bricks, not new.


Regards,
Peng


------------------ Original ------------------
From:  "Amar Tumballi";<amarts at gmail.com>;
Send time: Saturday, Dec 28, 2019 10:28 PM
To: "PSC"<1173701037 at qq.com>; 
Cc: "gluster-devel"<gluster-devel at gluster.org>; 
Subject:  Re: [Gluster-devel] Expanding Volume problem in old release 3.12.2



After expand, you need to run rebalance (at least the fix-layout) to get the files get distributed to newer bricks.

Regards,
Amar
--
https://kadalu.io




On Wed, 25 Dec, 2019, 9:34 AM PSC, <1173701037 at qq.com> wrote:

Hello,I have a glusterfs deployment, the version of which is 3.12.2.  When I expanded a volume, I encountered with a problem that new files wrote to volume will not appear on those bricks newly added to the volume. I mean new files will only wrote to original bricks of that volume (bricks before expand). Those new bricks will never used.
I made some test on the latest version of glusterfs, this problem disappeared. However, for stability concerning, I cannot upgrade to new version. I plan to made a patch on the old 3.12.2 glusterfs, just fix this one bug. Would you please tell me some information about it? 


Thank you very much!
_______________________________________________
 
 Community Meeting Calendar:
 
 APAC Schedule -
 Every 2nd and 4th Tuesday at 11:30 AM IST
 Bridge: https://bluejeans.com/441850968
 
 
 NA/EMEA Schedule -
 Every 1st and 3rd Tuesday at 01:00 PM EDT
 Bridge: https://bluejeans.com/441850968
 
 Gluster-devel mailing list
 Gluster-devel at gluster.org
 https://lists.gluster.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20191231/7e7c1b8d/attachment.html>