diff options
| author | corubba <corubba@gmx.de> | 2022-11-01 22:18:19 +0100 |
|---|---|---|
| committer | David Teigland <teigland@redhat.com> | 2022-11-11 12:08:59 -0600 |
| commit | 779fc3c0453d4a1abdfc62db740517467dbaf0e3 (patch) | |
| tree | e3820fd52e9d9cfcacb4b8f3de6d6925be3a5abb /lib | |
| parent | c77384785d3bd3d0c265220395dc392b52e62218 (diff) | |
| download | lvm2-779fc3c0453d4a1abdfc62db740517467dbaf0e3.tar.gz | |
report: adjust lv_active_remotely for shared VGs
Add a note to the manpage that lvmlockd is unable to determine
accurately and without side-effects whether a LV is remotely active.
Also change the value of the lv_active_remotely option from false to
undefined for shared VGs to distinctly communicate that inability to
users. Only for local VGs it can be definitely stated that they are not
remotely active.
Signed-off-by: corubba <corubba@gmx.de>
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/report/report.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/lib/report/report.c b/lib/report/report.c index 9172c1f0e..cb5fc93c8 100644 --- a/lib/report/report.c +++ b/lib/report/report.c @@ -3838,9 +3838,10 @@ static int _lvactiveremotely_disp(struct dm_report *rh, struct dm_pool *mem, struct dm_report_field *field, const void *data, void *private) { + const struct logical_volume *lv = (const struct logical_volume *) data; int active_remotely; - if (!activation()) + if (!activation() || vg_is_shared(lv->vg)) return _binary_undef_disp(rh, mem, field, private); active_remotely = 0; |