From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Zhao Heming <heming.zhao@suse.com>
Cc: teigland@sourceware.org
Subject: Re: [linux-lvm] [PATCH] lib/metadata: add new api lv_is_available()
Date: Fri, 28 Aug 2020 18:04:44 +0200 [thread overview]
Message-ID: <128df0c3-beeb-7f8a-e611-e1372185209c@redhat.com> (raw)
In-Reply-To: <1598544320-3198-1-git-send-email-heming.zhao@suse.com>
Dne 27. 08. 20 v 18:05 Zhao Heming napsal(a):
> It commit is enhancement for 1d0dc74f9147e3c1f3681efa4166cbe2edcb6571
> 1d0dc74f9147 only supports all raid type, this commit adds new api
> and extends support scope with linear/mirror type.
>
> This patch introduced a new flag NOT_AVAIL_LV, when a lv (includeing
> sub-lv or child-lv) doesn't work, this flag will set.
>
> With this patch, for linear type LV, one of two disks missing,
> lvdisplay will show
> from:
> LV Status available (partial)
> to:
> LV Status NOT available (partial)
>
Hi
LV 'available' has one simple meaning - LV is present in DM table.
Status is either available or NOT available.
Partially is completely different flag.
Please do not mix existing logic and existing script with some new unknown args.
Also note - preferred usage is 'lvs' - lvdisplay is mostly a backward
compatible tool with sometimes 'easier' to get some info - but normally all
the info should be obtained with 'lvs' tool which is highly configurable
and support much easier output for parsing in scripts.
(lvdisplay is missing TONS of attributes otherwise accessible with lvs)
Regards
Zdenek
next prev parent reply other threads:[~2020-08-28 16:04 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 [this message]
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
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=128df0c3-beeb-7f8a-e611-e1372185209c@redhat.com \
--to=zkabelac@redhat.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@redhat.com \
--cc=teigland@sourceware.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.