linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Xen <list@xenhideout.nl>
Subject: Re: [linux-lvm] Saying goodbye to LVM
Date: Wed, 07 Feb 2018 19:42:13 +0100	[thread overview]
Message-ID: <36e66a2bedd0821a7976d82c01c8660a@assyoma.it> (raw)
In-Reply-To: <483f0010a2bb04054c8434d70e0248a2@xenhideout.nl>

Il 01-02-2018 17:45 Xen ha scritto:
> You are probably happy about this, but...
> 
> I managed to get LVM to corrupt my data on Ubuntu Xenial 3 times now.
> 
> All of that is related to:
> 
> - LVM not checking or behaving correctly when a duplicate PV appears
> - LVM not checking or behaving correctly when a cache volume is out of
> sync with its origin.
> 
> In addition the thin DM target of kernel 3.x was so buggy I couldn't
> compile anything big without the system hanging.
> 
> I will probably become a ZFS user.
> 
> Goodbye, and thanks for all the fish.

I am both a LVM/ThinLVM and ZFS heavy user, so I hope to be impartial 
here...

LVM and its lvmthin counterpart are *rock solid* in my experience, 
except in the (very) edge case of full thin pool (this was lengthly 
discussed in the past, and both Zednek and Jonathan gave accurate 
suggestions on how to avoid that).

However, in my experience, the only distribution which keep updated 
version of lvm kernel and user space utilities is RHEL/CentOS. I found 
Debian and Ubuntu based distributions particularly *bad* at managing LVM 
and device mapper targets in general.

I am not using lvmcache, so I can not speak for it.

That said, ZFS really is outstanding (especially checksum and 
compression, albeit is sorely lacks reflinks). I really have high hopes 
for stratis (https://github.com/stratis-storage), which plan to provide 
ZFS-like feature using stacked device mapper targets (which our beloved 
LVM targets on top).

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

  parent reply	other threads:[~2018-02-07 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 16:45 [linux-lvm] Saying goodbye to LVM Xen
2018-02-02  2:49 ` John Stoffel
2018-02-07 18:42 ` Gionatan Danti [this message]
2018-02-07 19:21   ` pattonme
2018-02-07 20:37   ` Xen
2018-02-07 21:19     ` Gionatan Danti
2018-02-07 22:10       ` Xen
     [not found] <215644475.5896991.1518040435407.ref@mail.yahoo.com>
2018-02-07 21:53 ` matthew patton

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=36e66a2bedd0821a7976d82c01c8660a@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=linux-lvm@redhat.com \
    --cc=list@xenhideout.nl \
    /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).