[Gluster-users] Expanding brick size in glusterfs 3.7.11

[Jim Kinney]

I've expanded bricks using lvm and there was no problems at all with gluster seeing the change. The expansion was performed basically simultaneously on both existing bricks of a replica. I would expect the raid expansion to behave similarly.

On April 25, 2019 9:05:45 PM EDT, Pat Haley <phaley at mit.edu> wrote:
>
>Hi,
>
>Last summer we added a new brick to our gluster volume (running 
>glusterfs 3.7.11).  The new brick was a new server with with 12 of 24 
>disk bays filled (we couldn't afford to fill them all at the time).  
>These 12 disks are managed in a hardware RAID-6.  We have recently been
>
>able to purchase another 12 disks.  We would like to just add these new
>
>disks to the existing hardware RAID and thus expand the size of the 
>brick.  If we can successfully add them to the hardware RAID like this,
>
>will gluster have any problems with the expanded brick size?
>
>-- 
>
>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>Pat Haley                          Email:  phaley at mit.edu
>Center for Ocean Engineering       Phone:  (617) 253-6824
>Dept. of Mechanical Engineering    Fax:    (617) 253-8125
>MIT, Room 5-213                    http://web.mit.edu/phaley/www/
>77 Massachusetts Avenue
>Cambridge, MA  02139-4301
>
>_______________________________________________
>Gluster-users mailing list
>Gluster-users at gluster.org
>https://lists.gluster.org/mailman/listinfo/gluster-users

-- 
Sent from my Android device with K-9 Mail. All tyopes are thumb related and reflect authenticity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20190425/bde08b7b/attachment.html>