From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Zdenek Kabelac <zdenek.kabelac@gmail.com>
Subject: Re: [linux-lvm] LVM performance vs direct dm-thin
Date: Mon, 31 Jan 2022 08:47:34 +0100 [thread overview]
Message-ID: <c38e3b194516441f9fa08139b80fa0f6@assyoma.it> (raw)
In-Reply-To: <30ba3f0683afb9c3b60d96ac0019ced4ce9bb5b8.camel@gathman.org>
Il 2022-01-30 22:39 Stuart D. Gathman ha scritto:
> I use LVM as flexible partitions (i.e. only classic LVs, no thin pool).
> Classic LVs perform like partitions, literally using the same driver
> (device mapper) with a small number of extents, and are if anything
> more recoverable than partition tables. We used to put LVM on bare
> drives (like AIX did) - who needs a partition table? But on Wintel,
> you need a partition table for EFI and so that alien operating systems
> know there is something already on a disk.
Classical (fat) LVs are rock solid, but how do you cope with fast (maybe
rolling) snapshotting? This is the main selling point of thinlvm.
> Since we use LVs like partitions - mixing with btrfs is not an issue.
> Just use the LVs like partitions. I haven't tried ZFS on linux - it
> may have LVM like features that could fight with LVM. ZFS would be my
> first choice on a BSD box.
I broadly use ZFS - and yes, it is a wonderful tools. Than said, it has
its own gotcha. For example:
- snapshot rollback is a destructive operation (ie: after rollback, you
permanently lose the current filesystem state);
- clones (writable snapshots) depend on the read-only base image (ie: on
the original snapshot), which you can not delete until you have its
clones around.
Moreover, snapshotting/cloning a ZFS dataset (or volume) does not appear
to be significantly faster then LVM - sometime it requires ~1s,
depending on the load.
> We do not use LVM raid - but either run mdraid underneath, or let btrfs
> do it's data duplication thing with LVs on different spindles.
I always found btrfs very underperforming when facing random rewrite
workloads as VMs and DBs. Can I ask your experience?
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
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2022-01-31 7:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 20:34 [linux-lvm] LVM performance vs direct dm-thin Demi Marie Obenour
2022-01-29 21:32 ` Zdenek Kabelac
2022-01-30 0:32 ` Demi Marie Obenour
2022-01-30 10:52 ` Zdenek Kabelac
2022-01-30 16:45 ` Demi Marie Obenour
2022-01-30 17:43 ` Zdenek Kabelac
2022-01-30 20:27 ` Gionatan Danti
2022-01-30 21:17 ` Demi Marie Obenour
2022-01-31 7:52 ` Gionatan Danti
2022-02-02 2:09 ` Demi Marie Obenour
2022-02-02 10:04 ` Zdenek Kabelac
2022-02-03 0:23 ` Demi Marie Obenour
2022-02-03 12:04 ` Zdenek Kabelac
2022-02-03 12:04 ` Zdenek Kabelac
2022-01-30 21:39 ` Stuart D. Gathman
2022-01-30 22:14 ` Demi Marie Obenour
2022-01-31 21:29 ` Marian Csontos
2022-02-03 4:48 ` Demi Marie Obenour
2022-02-03 12:28 ` Zdenek Kabelac
2022-02-04 0:01 ` Demi Marie Obenour
2022-02-04 10:16 ` Zdenek Kabelac
2022-01-31 7:47 ` Gionatan Danti [this message]
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=c38e3b194516441f9fa08139b80fa0f6@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=zdenek.kabelac@gmail.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).