Linux LVM users
 help / color / mirror / Atom feed
From: Gionatan Danti <g.danti@assyoma.it>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: David, Teigland <teigland@redhat.com>,
	heming.zhao@suse.com,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] commit c527a0cbfc3 may have a bug
Date: Sun, 16 Feb 2020 16:17:37 +0100	[thread overview]
Message-ID: <5142ee226bc8527d4e0e7fcb61f6230d@assyoma.it> (raw)
In-Reply-To: <3966a334-3406-94c2-2fce-525b7e14c353@redhat.com>

Il 2020-02-15 21:19 Zdenek Kabelac ha scritto:
> IMHO ZFS is 'somewhat' slow to play with...
> and I've no idea how ZFS can resolve all correctness issues in 
> kernel...
> 
> Zdenek

Oh, it surely does *not* solve all correctness issues. Rather, having 
much simpler constrains (and use cases), it simply avoids many issues.

That said, what LVM achieve despite all abstraction layers and very 
different goals/use cases really is impressive.

So, thanks to the LVM team for the hard work!

-- 
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it [1]
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8

  reply	other threads:[~2020-02-16 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <098d6e8d-2d2c-5067-1435-eefd7e2d09bc@suse.com>
2020-02-14 15:18 ` [linux-lvm] commit c527a0cbfc3 may have a bug heming.zhao
2020-02-14 19:11 ` David Teigland
2020-02-14 19:34   ` Gionatan Danti
2020-02-14 20:40     ` David Teigland
2020-02-15  5:22       ` heming.zhao
2020-02-15 12:40       ` Zdenek Kabelac
2020-02-15 19:15         ` Gionatan Danti
2020-02-15 20:19           ` Zdenek Kabelac
2020-02-16 15:17             ` Gionatan Danti [this message]
2020-02-15 20:49           ` Chris Murphy
2020-02-16 15:28             ` Gionatan Danti
2020-02-15 19:07       ` Gionatan Danti

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=5142ee226bc8527d4e0e7fcb61f6230d@assyoma.it \
    --to=g.danti@assyoma.it \
    --cc=heming.zhao@suse.com \
    --cc=linux-lvm@redhat.com \
    --cc=teigland@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