From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
David Teigland <teigland@redhat.com>,
"heming.zhao@suse.com" <heming.zhao@suse.com>
Cc: Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] [PATCH] lib/metadata: add new api lv_is_available()
Date: Tue, 1 Sep 2020 13:43:42 +0200 [thread overview]
Message-ID: <d44e29ef-13ad-8218-ee50-ba992d7c0200@redhat.com> (raw)
In-Reply-To: <20200831223724.GB15486@redhat.com>
Dne 01. 09. 20 v 0:37 David Teigland napsal(a):
> On Sun, Aug 30, 2020 at 11:49:38PM +0800, heming.zhao@suse.com wrote:
>> in my opinion, the 'not available'
>
> We already use the word available/unavailable in other ways, so let's use
> "broken" for the moment, maybe we can find a better word.
>
> 'lvs -o broken' would report 0|1. Choosing an attr letter to represent
> that is not as important and can be decided on later.
I'd probably pick the 'opposite' word - i.e. lvs -o lv_usable -
but ATM - I'm still no sure how the meaning would differ from 'partial'
(which seems like it"s still missing separate lvs attribute shown only through
health attr column 9 letter).
But we probably need to look much deeper look at the meaning of partial -
which ATM is a simply transitivity enclosure over LV stack - while
particularly in raid case we need to probably go deeper and device into
categories.
This would also greatly help the current activation logic as well - but we
probably need to first acknowledge what is 'preferred' view from md raid side
- as these do not have an exact match.
Zdenek
prev parent reply other threads:[~2020-09-01 11:43 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
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 [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=d44e29ef-13ad-8218-ee50-ba992d7c0200@redhat.com \
--to=zkabelac@redhat.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@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).