mirror of
git://sourceware.org/git/lvm2.git
synced 2024-12-21 13:34:40 +03:00
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>
This commit is contained in:
parent
c77384785d
commit
779fc3c045
@ -3838,9 +3838,10 @@ static int _lvactiveremotely_disp(struct dm_report *rh, struct dm_pool *mem,
|
|||||||
struct dm_report_field *field,
|
struct dm_report_field *field,
|
||||||
const void *data, void *private)
|
const void *data, void *private)
|
||||||
{
|
{
|
||||||
|
const struct logical_volume *lv = (const struct logical_volume *) data;
|
||||||
int active_remotely;
|
int active_remotely;
|
||||||
|
|
||||||
if (!activation())
|
if (!activation() || vg_is_shared(lv->vg))
|
||||||
return _binary_undef_disp(rh, mem, field, private);
|
return _binary_undef_disp(rh, mem, field, private);
|
||||||
|
|
||||||
active_remotely = 0;
|
active_remotely = 0;
|
||||||
|
@ -878,6 +878,10 @@ If lvmlockd fails or is killed while in use, locks it held remain but are
|
|||||||
orphaned in the lock manager. lvmlockd can be restarted with an option to
|
orphaned in the lock manager. lvmlockd can be restarted with an option to
|
||||||
adopt the orphan locks from the previous instance of lvmlockd.
|
adopt the orphan locks from the previous instance of lvmlockd.
|
||||||
.
|
.
|
||||||
|
.IP \[bu]
|
||||||
|
The 'lvs' command does not report any remote state, because lvmlockd is
|
||||||
|
unable to passively check the remote active or lock state of an LV.
|
||||||
|
.
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
.
|
.
|
||||||
.BR lvm (8),
|
.BR lvm (8),
|
||||||
|
Loading…
Reference in New Issue
Block a user