From: David Teigland <teigland@redhat.com>
To: "heming.zhao" <heming.zhao@suse.com>
Cc: linux-lvm@redhat.com, Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [linux-lvm] [PATCH] lib/metadata: add new api lv_is_available()
Date: Tue, 1 Sep 2020 10:07:13 -0500 [thread overview]
Message-ID: <20200901150713.GB25039@redhat.com> (raw)
In-Reply-To: <c1796ea2-dcdb-230f-16f7-1d8acf470ed9@suse.com>
On Tue, Sep 01, 2020 at 05:09:23PM +0800, heming.zhao wrote:
> 'broken' is acceptable and good word.
> I'm only afraid end user don't know there is a new string item for lvs.
> like me, I just know the lv_health_status string item from Zdenek's mail. (sorry for my stupid)
I also like Zdenek's "usable", which seems to be closer to what we mean.
In addition to the reporting field can could be a new letter in the 9th lv
attr field. (We'd have to figure out the priority of this letter vs the
others.)
> I prefer lvm report status from the entire LV side.
> lvm provides virtual blocks to upper layer softwares, most of softwares use whole virtual disk.
Limit this to what lvm knows already. The field will represent whether
lvm believes the uppser layer can successfully do io to the entire LV.
Dave
next prev parent reply other threads:[~2020-09-01 15:07 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 [this message]
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=20200901150713.GB25039@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).