linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: Zhao Heming <heming.zhao@suse.com>, linux-lvm@redhat.com
Subject: Re: [linux-lvm] [PATCH] lib/metadata: add new api lv_is_available()
Date: Fri, 28 Aug 2020 13:26:08 -0500	[thread overview]
Message-ID: <20200828182608.GA17233@redhat.com> (raw)
In-Reply-To: <128df0c3-beeb-7f8a-e611-e1372185209c@redhat.com>

On Fri, Aug 28, 2020 at 06:04:44PM +0200, Zdenek Kabelac wrote:
> LV 'available' has one simple meaning - LV is present in DM table.
> Status is either available or NOT available.

LV Status can also be "suspended", so there's already some variation in
that field (which is why these free-form lvdisplay fields should be
avoided.)  But I agree, it's probably best to leave lvdisplay alone for
historical purposes and add anything new using just lvs fields.

Zhao, I think we should revert that commit, and come up with a new word to
describe this thing (which also needs a clear definition), and report it
in lvs.

Dave

  reply	other threads:[~2020-08-28 18:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 16:05 [linux-lvm] [PATCH] lib/metadata: add new api lv_is_available() Zhao Heming
2020-08-27 16:07 ` heming.zhao
2020-08-28 16:04 ` Zdenek Kabelac
2020-08-28 18:26   ` David Teigland [this message]
2020-08-30 15:49     ` heming.zhao
2020-08-30 17:06       ` Zdenek Kabelac
2020-08-31 22:37       ` David Teigland
2020-09-01  9:09         ` heming.zhao
2020-09-01 15:07           ` David Teigland
2020-09-01 16:15             ` heming.zhao
2020-09-01 11:43         ` Zdenek Kabelac

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=20200828182608.GA17233@redhat.com \
    --to=teigland@redhat.com \
    --cc=heming.zhao@suse.com \
    --cc=linux-lvm@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;
as well as URLs for NNTP newsgroup(s).