linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: John Stoffel <john@stoffel.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Saying goodbye to LVM
Date: Thu, 1 Feb 2018 21:49:58 -0500	[thread overview]
Message-ID: <A65313D2-8BFF-4B78-97C5-4FDEFE29AFBF@stoffel.org> (raw)
In-Reply-To: <483f0010a2bb04054c8434d70e0248a2@xenhideout.nl>

If you think zfs will be the answer... then good luck.  So where did a new PV come from that had the same UUID as the existing ones?  Basically the more details you give... then we can try to help.

But in any case, good luck.

Sent from my iPhone

> On Feb 1, 2018, at 11:45 AM, Xen <list@xenhideout.nl> wrote:
> 
> 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.
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2018-02-02  2:59 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 [this message]
2018-02-07 18:42 ` Gionatan Danti
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=A65313D2-8BFF-4B78-97C5-4FDEFE29AFBF@stoffel.org \
    --to=john@stoffel.org \
    --cc=linux-lvm@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).