** Description changed:
SRU justification
Impact : clustered lvm requires monitoring to be on which is hardcoded to off
so
it is currently impossible to import clustered LVM volume group even when
changing
the default in /etc/lvm/lvm.conf
- Fix : Revert the hardcoded value and force the default to 0 in
/etc/lvm/lvm.conf as
- the current LVM codebase can now make use of the value in /etc/lvm/lvm.conf
+ Fix : Actually read monitoring config value in /etc/lvm/lvm.conf when
+ dealing with clustered VGs.
- Test Case :
- - Create a one node cluster using CMAN and PACEMAKER.
- - Install CLVM and enable it ( lvmconf --enable-cluster )
- - Start CMAN, CLVM and PACEMAKER
- - Add an LVM device, create a Volume group and enable it.
+ Test Case :
+ - Create a one node cluster using CMAN and PACEMAKER.
+ - Install CLVM and enable it ( lvmconf --enable-cluster )
+ - Start CMAN, CLVM and PACEMAKER
+ - Add an LVM device, create a Volume group and enable it.
Without the fix, the user would see the following message :
# vgchange -a y data_vg
activation/monitoring=0 is incompatible with clustered Volume Group
"data_vg": Skipping.
- Regression : There should be no regression as it reverts the hardcoded
- value for monitoring and sets it up to 0 in /etc/lvm/lvm.conf which is
- the current default behavior.
+ Regression : clustered VGs should now be activated automatically and
+ correctly now, which maybe unexpected on some systems. No other defaults
+ have changed.
Description of the problem :
When trying to configure a clustered lvm2 using cman and clvm, clvm
start up and lvm commands fail with this error:
# vgchange -a y data_vg
activation/monitoring=0 is incompatible with clustered Volume Group
"data_vg": Skipping.
if I use "--monitor y" then the command works as expected.
# vgchange -a y --monitor y data_vg
1 logical volume(s) in volume group "data_vg" now active
activation/monitoring is set to 1 in lvm.conf
The biggest problem is that I can't do LVM manipulation via interfaces
such as virt-manager.
Here is the lvm.conf dump:
# lvm dumpconfig
devices {
dir="/dev"
scan="/dev"
preferred_names=[]
filter=["a|drbd.*|", "r|.*|"]
cache_dir="/etc/lvm/cache"
cache_file_prefix=""
write_cache_state=1
sysfs_scan=1
md_component_detection=1
md_chunk_alignment=1
data_alignment_detection=1
data_alignment=0
data_alignment_offset_detection=1
ignore_suspended_devices=0
}
dmeventd {
mirror_library="libdevmapper-event-lvm2mirror.so"
snapshot_library="libdevmapper-event-lvm2snapshot.so"
}
activation {
udev_sync=1
udev_rules=1
missing_stripe_filler="error"
reserved_stack=256
reserved_memory=8192
process_priority=-18
mirror_region_size=512
readahead="auto"
mirror_log_fault_policy="allocate"
mirror_image_fault_policy="remove"
use_mlockall=0
monitoring=1
polling_interval=15
}
global {
umask=63
test=0
units="h"
si_unit_consistency=1
activation=1
proc="/proc"
locking_type=3
wait_for_locks=1
fallback_to_clustered_locking=1
fallback_to_local_locking=1
locking_dir="/var/lock/lvm"
prioritise_write_locks=1
abort_on_internal_errors=0
}
shell {
history_size=100
}
backup {
backup=1
backup_dir="/etc/lvm/backup"
archive=1
archive_dir="/etc/lvm/archive"
retain_min=10
retain_days=30
}
log {
verbose=0
syslog=1
overwrite=0
level=0
indent=1
command_names=0
prefix=" "
activation=1
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833368
Title:
clustered lvm commands fail with "activation/monitoring=0 is
incompatible with clustered Volume Group" error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
