<div dir="ltr">Apologies, it's XFS so would be an xfs_growfs<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 1, 2016 at 10:58 AM, Matt Wells <span dir="ltr"><<a href="mailto:matt.wells@mosaic451.com" target="_blank">matt.wells@mosaic451.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div data-smartmail="gmail_signature"><div dir="ltr"><div>Hi everyone, I had a quick question that I really needed to bounce off someone; one of those measure twice cut once moments.</div><div><br></div><div>My primary datastore is on a gluster volume and the short story is I'm going to grow it. I've thought of two options</div><div><br></div><div>1 - add a brick with the new space</div><div><div>** Was wondering from the gluster point of view if anyone had a best practice for this. I've looked around and find many people explaining their stories but not a definitive best practices.</div></div><div><br></div><div><br></div><div>2 - as I'm sitting atop LVMs grow the LVM. </div><div>** This is the one that makes me a little nervous. I've done many resize2fs and never had issues, but I've never had gluster running atop that volume and my VM's atop that. Has anyone had any experiences they could share?<br></div><div><br></div><div>Thanks all - </div><span class=""><font color="#888888"><div>Wells</div></font></span></div></div>
</div>
</blockquote></div><br><br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br><br><br><br><br><br><br><br><br><br><br><br><br></div></div></div>
</div></div>