linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Stuart D Gathman <stuart@gathman.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Gionatan Danti <g.danti@assyoma.it>,
	Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] lvm limitations
Date: Tue, 15 Sep 2020 17:30:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LRH.2.23.451.2009151726030.32184@mail.gathman.org> (raw)
In-Reply-To: <257A9B1C-04AC-4EDE-9671-9E7A60104F9F@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

On Tue, 15 Sep 2020, Tomas Dalebjörk wrote:

> ok, lets say that I have 10 LV on a server, and want create a thin lv
> snapshot every hour and keep that for 30 days that would be 24h *
> 30days * 10lv = 720 lv

> if I want to keep snapshot copies from more nodes, to serve a single
> repository of snapshot copies, than these would easily become several
> hundred thousands of lv

> not sure if this is a good idea, but I guess it can be very useful in
> some sense as block level incremental forever and instant recovery can
> be implemented for open sourced based applications
>
> what reflections do you have on this idea?

My feeling is that btrfs is a better solution for the hourly snapshots.
(Unless you are testing a filesystem :-)

I find "classic" LVs a robust replacement for partitions that are easily
resized without moving data around.  I would be more likely to try
RAID features on classic LVs than thin LVs.

  reply	other threads:[~2020-09-15 22:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29 23:25 [linux-lvm] lvm limitations Tomas Dalebjörk
2020-08-30 17:33 ` Zdenek Kabelac
2020-08-30 18:01   ` Gionatan Danti
2020-08-30 19:30     ` Zdenek Kabelac
2020-09-01 13:21       ` Gionatan Danti
2020-09-15 19:16         ` Tomas Dalebjörk
2020-09-15 20:08           ` Zdenek Kabelac
2020-09-15 21:24             ` Tomas Dalebjörk
2020-09-15 21:30               ` Stuart D Gathman [this message]
2020-09-15 22:24                 ` Gionatan Danti
2020-09-15 21:47               ` Zdenek Kabelac
2020-09-15 22:26                 ` Gionatan Danti
2020-09-16  4:25                   ` Tomas Dalebjörk
2020-09-17 19:24                     ` Zdenek Kabelac
2020-09-16  4:31                   ` Tomas Dalebjörk
2020-09-16  4:58                   ` Tomas Dalebjörk
2020-09-17 19:17                     ` Zdenek Kabelac
2020-09-17 19:32                   ` Zdenek Kabelac
2020-09-14  6:03 Tomas Dalebjörk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.23.451.2009151726030.32184@mail.gathman.org \
    --to=stuart@gathman.org \
    --cc=g.danti@assyoma.it \
    --cc=linux-lvm@redhat.com \
    --cc=zkabelac@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).