From: Gionatan Danti <g.danti@assyoma.it>
To: Stuart D Gathman <stuart@gathman.org>
Cc: Kabelac <zkabelac@redhat.com>,
Zdenek,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm limitations
Date: Wed, 16 Sep 2020 00:24:05 +0200 [thread overview]
Message-ID: <1f3665cda84cb1fe3bbb1a0ad52b588c@assyoma.it> (raw)
In-Reply-To: <alpine.LRH.2.23.451.2009151726030.32184@mail.gathman.org>
Il 2020-09-15 23:30 Stuart D Gathman ha scritto:
> My feeling is that btrfs is a better solution for the hourly snapshots.
> (Unless you are testing a filesystem :-)
For fileserver duty, sure - btrfs is adequate.
For storing VMs and/or databases - no way, thinvol is much faster
Side note: many btrfs guides suggest disabling CoW fixes btrfs
performance issue. Reality is that noCoW fixes them partially at best,
while at the same time disabling all advanced feature (checksum,
compression, etc). Snapshot automatically re-enable CoW for the
overwritten data.
> 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.
I agree for classical LVM.
However thinvols permit much more interesting scenario.
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-15 22:24 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 [this message]
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=1f3665cda84cb1fe3bbb1a0ad52b588c@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=stuart@gathman.org \
--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).