shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-21 13:34:40 +03:00
Code Releases Activity

activation: if LV inactive and non-clustered, do not issue "Cannot deactivate" on -aln

Browse Source 
The message "Cannot deactivate remotely exclusive device locally." makes
sense only for clustered LV. If the LV is non-clustered, then it's
always exclusive by definition and if it's already deactivated, this
message pops up inappropriately as those two conditions are met.

So issue the message only if the conditions are met AND we have clustered VG.
This commit is contained in:
Peter Rajnoha 2014-08-07 16:44:09 +02:00
parent ea662ca060
commit c52c9a1e31
2 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
WHATS_NEW
View File

@ -1,5 +1,6 @@
Version 2.02.110 -
==================================
If LV inactive and non-clustered, do not issue "Cannot deactivate" on -aln.
Remove spurious "Skipping mirror LV" message on pvmove of clustered mirror.
Version 2.02.109 - 5th August 2014

2
lib/metadata/lv.c
View File

@ -859,7 +859,7 @@ deactivate:
return_0;
break;
case CHANGE_ALN:
if (_lv_is_exclusive(lv)) {
if (vg_is_clustered(lv->vg) && _lv_is_exclusive(lv)) {
if (!lv_is_active_locally(lv)) {
log_error("Cannot deactivate remotely exclusive device locally.");
return 0;