<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Apr 8, 2019, 21:47 Strahil <<a href="mailto:hunter86_bg@yahoo.com">hunter86_bg@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Correct me if I'm wrong but thin LVM is needed for creation of snapshots.</p></blockquote></div></div><div dir="auto">Yes, you need thin provisioned logical volumes for gluster snapshots. Actually, gluster snapshots are lvm snapshots under the hood.</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">I am a new gluster user , but I don't see any LVM issues so far.</p></blockquote></div></div><div dir="auto">Neither me</div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">Best Regards,<br>
Strahil Nikolov</p>
<div class="m_-5366751841947145838quote">On Apr 8, 2019 21:15, Alex K <<a href="mailto:rightkicktech@gmail.com" target="_blank" rel="noreferrer">rightkicktech@gmail.com</a>> wrote:<br type="attribution"><blockquote class="m_-5366751841947145838quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>I use gluster on top of lvm for several years without any issues. </div><br><div class="m_-5366751841947145838elided-text"><div dir="ltr">On Mon, Apr 8, 2019, 10:43 Felix Kölzow <<a href="mailto:felix.koelzow@gmx.de" target="_blank" rel="noreferrer">felix.koelzow@gmx.de</a>> wrote:<br></div><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p>Thank you very much for your response.</p>
<p>I fully agree that using LVM has great advantages. Maybe there is
a misunderstanding,</p>
<p>but I really got the recommendation to not use (normal) LVM in
combination with gluster to <br>
</p>
<p>increase the volume. <b>Maybe someone in the community has some
good or bad experience</b></p>
<p><b>using LVM and gluster in combination.</b> So please let me
know :)</p>
<p><br>
</p>
<p>
</p><blockquote>One of the arguments for things like
Gluster and Ceph is that you can many storage nodes that operate
in parallel so that the ideal is a very large number of small
drive arrays over a small number of very large drive arrays.
</blockquote>
I also agree we that. In our case, we actually plan to get Redhat
Gluster Storage Support and an increase of <br>
<p>storage nodes would mean an increase of support costs while the
same amount of storage volume is available.<br>
</p>
<p>So we are looking for a reasonable compromise.</p>
<p>Felix<br>
</p>
<div>On 03.04.19 17:12, Alvin Starr wrote:<br>
</div>
<blockquote>As a
general rule I always suggest using LVM.
<br>
I have had LVM save my career a few times.
<br>
I believe that if you wish to use Gluster snapshots then the
underlying system needs to be a thinly provisioned LVM volume.
<br>
<br>
Adding storage space to an LVM is easy and all modern file-systems
support online growing so it is easy to grow a file-system.
<br>
<br>
If you have directory trees that are very deep and wide then you
may want to put a bit of thought into how you configure your
Gluster installation.
<br>
We have a volume with about 50M files and something like an xfs
dump or rsync of the underlying filesystem will take close to a
day but copying the data over Gluster takes weeks.
<br>
This is a problem with all clustered file systems because there is
extra locking and co-ordination required for file operations.
<br>
<br>
Also you need to realize that the performance of something like
the powervault is limited to the speed of the connection to your
server.
<br>
So that a single SAS link is limited to 6Gb(for example) and so is
your disk array but most internal raid controllers will support
the number of ports * 6Gb.
<br>
This means that a computer with 12 drives in the front will access
disk faster than a system with a 12 drive disk array attached by a
few SAS links.
<br>
<br>
One of the arguments for things like Gluster and Ceph is that you
can many storage nodes that operate in parallel so that the ideal
is a very large number of small drive arrays over a small number
of very large drive arrays.
<br>
<br>
<br>
On 4/3/19 10:20 AM, kbh-admin wrote:
<br>
<blockquote>Hello Gluster-Community,
<br>
<br>
<br>
we consider to build several Gluster-servers and have a question
regarding lvm and Glusterfs.
<br>
<br>
<br>
Scenario 1: Snapshots
<br>
<br>
Of course, taking snapshots is a good capability and we want to
use lvm for that.
<br>
<br>
<br>
Scenaraio 2: Increase Gluster volume
<br>
<br>
We want to increase the Gluster volume by adding hdd's and/or by
adding
<br>
<br>
dell powervaults later. We got the recommendation to set up a
new Gluster volume
<br>
<br>
for the powervaults and don't use lvm in that case (lvresize
....) .
<br>
<br>
<br>
What would you suggest and how do you manage both lvm and
Glusterfs together?
<br>
<br>
<br>
Thanks in advance.
<br>
<br>
<br>
Felix
<br>
<br>
_______________________________________________
<br>
Gluster-users mailing list
<br>
<a href="mailto:Gluster-users@Gluster.org" target="_blank" rel="noreferrer"></a></blockquote></blockquote></div></blockquote></div></blockquote></div></blockquote></div></div></div>