From: "Tomas Dalebjörk" <tomas.dalebjork@gmail.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: LVM general discussion and development <linux-lvm@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] lvm limitations
Date: Wed, 16 Sep 2020 06:31:40 +0200 [thread overview]
Message-ID: <80241AC1-65CF-45B8-A370-DC7E56F3F675@gmail.com> (raw)
In-Reply-To: <cf779b76e25707b8ec3361f55318a1c7@assyoma.it>
I also consider to build this application as an open source project
but of course it would be good to have some sponsors
I have been working as a C developer for over 35 years, and have created kernel drivers for both commercial and open source operating system
and developed several commercial applications that have been used on many places by banks, military, education etc
do you know where to get sponsors from if any are likely to help?
regards Tomas
Sent from my iPhone
> On 16 Sep 2020, at 00:26, Gionatan Danti <g.danti@assyoma.it> wrote:
>
> Il 2020-09-15 23:47 Zdenek Kabelac ha scritto:
>> You likely don't need such amount of 'snapshots' and you will need to
>> implement something to remove snapshot without need, so i.e. after a
>> day you will keep maybe 'every-4-hour' and after couple days maybe
>> only a day-level snapshot. After a month per-week and so one.
>
> Agree. "Snapshot-thinning" is an essential part of snapshot management.
>
>> Speaking of thin volumes - there can be at most 2^24 thin devices
>> (this is hard limit you've ask for ;)) - but you have only ~16GiB of
>> metadata to store all of them - which gives you ~1KiB of data per such
>> volume -
>> quite frankly this is not too much - unless as said - your volumes
>> are not changed at all - but then why you would be building all this...
>> That all said - if you really need that intensive amount of snapshoting,
>> lvm2 is likely not for you - and you will need to build something on your own,
>> as you will need way more efficient and 'targeted' solution for your purpose.
>
> Thinvols are not activated by default - this means it should be not a big problem managing some hundreds of them, as the OP ask. Or am I missing something?
>
> Regards.
>
> --
> Danti Gionatan
> Supporto Tecnico
> Assyoma S.r.l. - www.assyoma.it
> email: g.danti@assyoma.it - info@assyoma.it
> GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2020-09-16 4:31 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
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 [this message]
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=80241AC1-65CF-45B8-A370-DC7E56F3F675@gmail.com \
--to=tomas.dalebjork@gmail.com \
--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).