[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Used a precise canonistack instance with a volume attached. Configured cman/pacemaker single node instance using https://wiki.ubuntu.com/ClusterStack/Precise Verified that clvm clustered vg can be activated when they are clustered and activation/monitoring=1 and without specifying --monitor y. Verified that --monitor y still works to override activation/monitoring=0 setting. Verified that non-clustered VGs still work. ** Tags added: verification-precise-done -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
This bug was fixed in the package lvm2 - 2.02.66-4ubuntu7.2 --- lvm2 (2.02.66-4ubuntu7.2) precise; urgency=low * Honour monitoring=1 config option in /etc/lvm/lvm.conf when using clustered VGs (LP: #833368). * /etc/init.d/clvm status now exits with code 3, if clvm is not running, as per LSB specification. (LP: #91) -- Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Wed, 06 Feb 2013 10:34:32 + ** Changed in: lvm2 (Ubuntu Precise) Status: Fix Committed = Fix Released -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Tags removed: verification-needed ** Tags added: verification-done -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Changed in: lvm2 (Ubuntu Precise) Status: In Progress = Fix Committed ** Tags added: verification-needed -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Branch linked: lp:ubuntu/precise-proposed/lvm2 -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
This package has been uploaded into precise-proposed unapproved queue, pending acceptance by SRU team. lvm2 (2.02.66-4ubuntu7.2) precise; urgency=low * Honour monitoring=1 config option in /etc/lvm/lvm.conf when using clustered VGs (LP: #833368). * /etc/init.d/clvm status now exits with code 3, if clvm is not running, as per LSB specification. (LP: #91) Date: Wed, 06 Feb 2013 10:34:32 + Changed-By: Dmitrijs Ledkovs dmitrij.led...@ubuntu.com Maintainer: Ubuntu Core Developers ubuntu-devel-disc...@lists.ubuntu.com https://launchpad.net/ubuntu/precise/+source/lvm2/2.02.66-4ubuntu7.2 == OK: lvm2_2.02.66.orig.tar.gz OK: lvm2_2.02.66-4ubuntu7.2.debian.tar.gz OK: lvm2_2.02.66-4ubuntu7.2.dsc - Component: main Section: admin -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
I disagree with the proposed fix in https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/comments/46 Due to the reason behind this patch - https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/comments/11 On the other-hand not many people have clustered vgs setup, and if they do we can require dmeventd running. Thus i'll propose a patch for precise to read monitoring value from /etc/lvm/lvm.conf if vg_is_clustered are detected. I'll first test these assumptions with juju using precise machines to make sure it solves this bug and doesn't change lvm behaviour for non- clustered case. Regards, Dmitrijs. ** Changed in: lvm2 (Ubuntu Precise) Assignee: Louis Bouchard (louis-bouchard) = Dmitrijs Ledkovs (xnox) ** Changed in: lvm2 (Ubuntu Precise) Importance: Undecided = High -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@ louis-bouchard the changelog entry in your debdiff points to precise instead of precise-proposed, could you update that ? -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
New debdiff with precise-proposed in the changelog ** Patch removed: lvm2_2.02.66-4ubuntu7.2.debdiff https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+attachment/3463983/+files/lvm2_2.02.66-4ubuntu7.2.debdiff ** Patch added: lvm2_2.02.66-4ubuntu7.2.debdiff https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+attachment/3498349/+files/lvm2_2.02.66-4ubuntu7.2.debdiff -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
On 14.01.2013 15:28, Dmitrijs Ledkovs wrote:: I did cite my sources, by copy pasting Debian changelog entry as uploaded into Debian for the lvm2 package. TBH, I find it surprising that anyone can claim that clvm never worked. It works at least since 2008 - it's when I started using it on production machines. Claim that clvm is dead upstream makes me wonder - is this a hoax? Clvm is not dead. It's quite the opposite. We should fork the package or help Debian maintainer find the truth :) -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@xnox No matter what happens to upstream/upcoming Ubuntu versions, clvm is part of Precise and supported for its LTS life. This shouldn't impact this SRU unless I'm mistaken -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@ Nec I did cite my sources, by copy pasting Debian changelog entry as uploaded into Debian for the lvm2 package. @ louis-bouchard I know that LTS is not going to change with respect to feature set. I just wanted to get feedback, if we still want to continue provide clvm in Ubuntu, despite Debian not shipping it. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
As a user of Ubuntu I would like to see it supported. I use it extensively on physical hosts to support virtual servers. It's also particularly useful for OCFS2, GFS/GFS2, ceph etc. Apparently this removal could brick servers using the the cluster feature as well (debian bug #697676.) -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Indeed, I don't get it ! How is Debian planning to do to propose a clustered use of a filesystem amongst more than 2 nodes? As Mark said, the number of broken dependencies is large, I don't understand this choice. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Too bad! I based part of my work on this. Having to leave debian/ubuntu universe to be forced to return to redhat/fedora/centos is not the greatest joy of my day... -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@xnox Anyway, may you cite your sources please ? -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
On Sat, Jan 12, 2013 at 12:03:21AM -, Dmitrijs Ledkovs wrote: Debian dropped clustered lvm2 support. * Drop cluster (clvm) support. It never properly worked and is more dead than alive. -- Bastian Blank wa...@debian.org Wed, 02 Jan 2013 11:11:41 +0100 Do we still want it in Ubuntu? It it certainly not dead upstream and does work properly. It remains supported in Fedora/Red Hat Enterprise Linux/CentOS and presumably in many other distributions too. Alasdair -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Debian dropped clustered lvm2 support. lvm2 (2.02.95-6) unstable; urgency=low * Drop cluster (clvm) support. It never properly worked and is more dead than alive. -- Bastian Blank wa...@debian.org Wed, 02 Jan 2013 11:11:41 +0100 Do we still want it in Ubuntu? -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
caribou xnox: it's already fixed in Q R Adjusted statuses. ** Also affects: lvm2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: resource-agents (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: resource-agents (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Raring) Importance: Undecided Assignee: Dmitrijs Ledkovs (xnox) Status: Confirmed ** Also affects: resource-agents (Ubuntu Raring) Importance: Undecided Assignee: Ante Karamatić (ivoks) Status: In Progress ** Changed in: lvm2 (Ubuntu Precise) Status: New = Confirmed ** Changed in: lvm2 (Ubuntu Raring) Assignee: Dmitrijs Ledkovs (xnox) = (unassigned) ** Changed in: lvm2 (Ubuntu Quantal) Status: New = Invalid ** Changed in: lvm2 (Ubuntu Raring) Status: Confirmed = Invalid ** Tags added: precise -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Changed in: lvm2 (Ubuntu Precise) Assignee: (unassigned) = Louis Bouchard (louis-bouchard) ** Changed in: resource-agents (Ubuntu Precise) Assignee: (unassigned) = Louis Bouchard (louis-bouchard) ** Changed in: lvm2 (Ubuntu Quantal) Assignee: (unassigned) = Louis Bouchard (louis-bouchard) ** Changed in: lvm2 (Ubuntu Raring) Assignee: (unassigned) = Louis Bouchard (louis-bouchard) ** Changed in: resource-agents (Ubuntu Quantal) Assignee: (unassigned) = Louis Bouchard (louis-bouchard) -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Description changed:
- # lsb_release -rd
- Description:Ubuntu 11.04
- Release:11.04
+ SRU justification
- # apt-cache policy lvm2
- lvm2:
- Installed: 2.02.66-4ubuntu2
- Candidate: 2.02.66-4ubuntu2
- Version table:
- *** 2.02.66-4ubuntu2 0
- 500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
- 100 /var/lib/dpkg/status
+ 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
- # apt-cache policy clvm
- clvm:
- Installed: 2.02.66-4ubuntu2
- Candidate: 2.02.66-4ubuntu2
- Version table:
- *** 2.02.66-4ubuntu2 0
- 500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
- 100 /var/lib/dpkg/status
+ 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
+ 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.
- # apt-cache policy libdevmapper1.02.1
- libdevmapper1.02.1:
- Installed: 2:1.02.48-4ubuntu2
- Candidate: 2:1.02.48-4ubuntu2
- Version table:
- *** 2:1.02.48-4ubuntu2 0
- 500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
- 100 /var/lib/dpkg/status
+ 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.
- When trying to configure a clustered lvm2 using cman and clvm, clvm start up
and lvm commands fail with this error:
+ 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.
-
+ 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
}
** Changed in: resource-agents (Ubuntu Precise)
Status: New = Invalid
** Changed in: resource-agents (Ubuntu Quantal)
Status: New = Invalid
** Changed in: resource-agents (Ubuntu Raring)
Status: In Progress = Invalid
** Changed in: lvm2 (Ubuntu Precise)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
debdiff for the proposed fix tested on 12.04 precise ** Patch added: lvm2_2.02.66-4ubuntu7.2.debdiff https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+attachment/3463983/+files/lvm2_2.02.66-4ubuntu7.2.debdiff -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@robert You may want to revert your changes if possible to test the fix once it becomes available in the -proposed pocket. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Branch linked: lp:~louis- bouchard/ubuntu/precise/lvm2/lvm2-lp833368-precise -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
We are experiencing this bug as well, and are very keen to see a fix. How is work going on this? The two work-arounds suggested above, have not succeeded for us; a) add the 'ppa:ivoks/ha' respoitory and pull the clvm from there. b) Manually edit /etc./init.d/clvm to add the --monitor y option to the vgchange commands in the do_activate routine Has anyone identified a work-around that works? If there is one, then can you help us in the short term and share it please? -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@robert We did not use the ppa but changing all occurrences of vgchange in
the clvm script has been working so far.
Sent from my Google Nexus tablet
On Nov 22, 2012 1:11 PM, Robert McGrath robert.mcgr...@hogarthww.com
wrote:
We are experiencing this bug as well, and are very keen to see a fix.
How is work going on this?
The two work-arounds suggested above, have not succeeded for us;
a) add the 'ppa:ivoks/ha' respoitory and pull the clvm from there.
b) Manually edit /etc./init.d/clvm to add the --monitor y option to
the vgchange commands in the do_activate routine
Has anyone identified a work-around that works?
If there is one, then can you help us in the short term and share it
please?
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/833368
Title:
clustered lvm commands fail with activation/monitoring=0 is
incompatible with clustered Volume Group error
Status in “lvm2” package in Ubuntu:
Confirmed
Status in “resource-agents” package in Ubuntu:
In Progress
Bug description:
# lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
# apt-cache policy lvm2
lvm2:
Installed: 2.02.66-4ubuntu2
Candidate: 2.02.66-4ubuntu2
Version table:
*** 2.02.66-4ubuntu2 0
500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy clvm
clvm:
Installed: 2.02.66-4ubuntu2
Candidate: 2.02.66-4ubuntu2
Version table:
*** 2.02.66-4ubuntu2 0
500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy libdevmapper1.02.1
libdevmapper1.02.1:
Installed: 2:1.02.48-4ubuntu2
Candidate: 2:1.02.48-4ubuntu2
Version table:
*** 2:1.02.48-4ubuntu2 0
500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
100 /var/lib/dpkg/status
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
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions
--
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
--
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
We have a two node cluster, and the work-around of hacking --monitor y into /etc/init.d/clvm has failed, but not totally. The operating system lives on VG0 (not clustered), and that is ok. There is a single clustered volume group called VGclust0. In that VG there are only three logical volumes lvmetadata lvdata lvbackup With the work-around/hack we have two LV's reporting available, and one NOT available I hope this information helps. -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
@robert
That doesn't sound like the same issue. Either no lvs would show or all of
them.
The actual error messages you're seeing if any could be helpful. The output
of pvs -vv, vgs -vv and lvs -vv would be helpful as well.
On Thu, Nov 22, 2012 at 1:35 PM, Robert McGrath
robert.mcgr...@hogarthww.com wrote:
We have a two node cluster, and the work-around of hacking --monitor
y into /etc/init.d/clvm has failed, but not totally.
The operating system lives on VG0 (not clustered), and that is ok.
There is a single clustered volume group called VGclust0.
In that VG there are only three logical volumes
lvmetadata
lvdata
lvbackup
With the work-around/hack we have two LV's reporting available, and one
NOT available
I hope this information helps.
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/833368
Title:
clustered lvm commands fail with activation/monitoring=0 is
incompatible with clustered Volume Group error
Status in “lvm2” package in Ubuntu:
Confirmed
Status in “resource-agents” package in Ubuntu:
In Progress
Bug description:
# lsb_release -rd
Description:Ubuntu 11.04
Release:11.04
# apt-cache policy lvm2
lvm2:
Installed: 2.02.66-4ubuntu2
Candidate: 2.02.66-4ubuntu2
Version table:
*** 2.02.66-4ubuntu2 0
500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy clvm
clvm:
Installed: 2.02.66-4ubuntu2
Candidate: 2.02.66-4ubuntu2
Version table:
*** 2.02.66-4ubuntu2 0
500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
100 /var/lib/dpkg/status
# apt-cache policy libdevmapper1.02.1
libdevmapper1.02.1:
Installed: 2:1.02.48-4ubuntu2
Candidate: 2:1.02.48-4ubuntu2
Version table:
*** 2:1.02.48-4ubuntu2 0
500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
100 /var/lib/dpkg/status
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
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/833368/+subscriptions
--
Tais Plougmann Hansen
OSD Consulting ApS
osd.dk
Tel: +45 78101078
CVR: DK31332737
--
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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
After a clean boot (no hacks or work-arounds applied), this is the output of crm configure show node gswhdesv01-nfs2 node ixlhdesv01-nfs1 primitive resCLVMd ocf:lvm2:clvmd \ params daemon_timeout=100 \ op start interval=0 timeout=90s \ op stop interval=0 timeout=100s primitive resDLM ocf:pacemaker:controld \ params daemon=dlm_controld \ op monitor interval=120s \ op start interval=0 timeout=90s \ op stop interval=0 timeout=100s primitive resFidoData ocf:heartbeat:Filesystem \ params device=/dev/VGshared00/lvFidoData directory=/opt/hogarth/FidoData fstype=gfs2 \ op monitor interval=14s timeout=40 \ op start interval=0 timeout=60 \ op stop interval=0 timeout=60 \ meta resource-stickiness=20 primitive resGFSD ocf:pacemaker:controld \ params daemon=gfs_controld args= \ op monitor interval=120s \ op start interval=0 timeout=90s \ op stop interval=0 timeout=100s primitive resGFSNFSmeta ocf:heartbeat:Filesystem \ params device=/dev/VGshared00/NFSmetadata directory=/opt/hogarth/NFSmetadata fstype=gfs2 \ op monitor interval=14s timeout=40 \ op start interval=0 timeout=60 \ op stop interval=0 timeout=60 \ meta resource-stickiness=30 target-role=Started primitive resSQLBckp ocf:heartbeat:Filesystem \ params device=/dev/VGshared00/lvSQLBckp directory=/opt/hogarth/SQLBckp fstype=gfs2 \ op monitor interval=14s timeout=40 \ op start interval=0 timeout=60 \ op stop interval=0 timeout=60 \ meta resource-stickiness=25 primitive resVGshared00 ocf:heartbeat:LVM \ params volgrpname=VGshared00 \ op monitor interval=10 timeout=50 depth=0 \ op start interval=0 timeout=P140S \ op stop interval=0 timeout=P40S \ meta resource-stickiness=10 target-role=Started is-managed=true primitive stonith_sbd stonith:external/sbd \ params sbd_device=/dev/mapper/HSBC-NFS-STORAGE-part1 clone cloneCLVMd resCLVMd \ meta globally-unique=false target-role=Started interleave=true clone cloneDLM resDLM \ meta globally-unique=false target-role=Started interleave=true clone cloneFidoData resFidoData \ meta interleave=true ordered=true target-role=Started clone cloneGFSD resGFSD \ meta globally-unique=false interleave=true target-role=Started clone cloneSQLBckp resSQLBckp \ meta interleave=true ordered=true target-role=Started clone cstonith_sbd stonith_sbd \ meta globally-unique=false target-role=Started interleave=true colocation colGFSDDLM inf: cloneGFSD cloneDLM colocation colGFSFidoData inf: cloneFidoData cloneGFSD colocation colGFSSQLBckp inf: cloneSQLBckp cloneGFSD order ordDLMGFSD 0: cloneDLM cloneGFSD order ordLVMgfs 1: resVGshared00 cloneGFSD property $id=cib-bootstrap-options \ dc-version=1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c \ cluster-infrastructure=cman \ expected-quorum-votes=2 \ stonith-enabled=false \ last-lrm-refresh=1353588948 This is a piece from /var/log/syslog at the time of boot Nov 22 13:54:09 ixlhdesv01-nfs1 LVM[3841]: INFO: Deactivating volume group VGshared00 Nov 22 13:54:09 ixlhdesv01-nfs1 LVM[3841]: ERROR: activation/monitoring=0 is incompatible with clustered Volume Group VGshared00: Skipping. This is the output of pvs -vv from node1 Setting global/locking_type to 3 Setting global/wait_for_locks to 1 Cluster locking selected. report/aligned not found in config: defaulting to 1 report/buffered not found in config: defaulting to 1 report/headings not found in config: defaulting to 1 report/separator not found in config: defaulting to report/prefixes not found in config: defaulting to 0 report/quoted not found in config: defaulting to 1 report/columns_as_rows not found in config: defaulting to 0 report/pvs_sort not found in config: defaulting to pv_name report/pvs_cols_verbose not found in config: defaulting to pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid Locking VG P_#global CR (VG) (0x1) Scanning for physical volume names /dev/ram0: No label detected /dev/ram1: No label detected /dev/sda1: No label detected /dev/ram2: No label detected /dev/sda2: No label detected /dev/ram3: No label detected /dev/sda3: lvm2 label detected /dev/ram4: No label detected /dev/ram5: No label detected /dev/ram6: No label detected /dev/dm-6: No label detected /dev/ram7: No label detected /dev/ram8: No label detected /dev/dm-8: lvm2 label detected /dev/ram9: No label detected /dev/dm-9: lvm2 label detected /dev/ram10: No label detected /dev/dm-10: lvm2 label detected /dev/ram11: No label detected /dev/ram12: No label detected /dev/ram13: No label detected
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
On 22.11.2012 15:05, Robert McGrath wrote:: primitive resCLVMd ocf:lvm2:clvmd \ params daemon_timeout=100 \ op start interval=0 timeout=90s \ op stop interval=0 timeout=100s You aren't using clvmd init.d script. You are using clvmd OCF. Edit /usr/lib/ocf/resource.d/lvm2/clvmd and add --monitor y to appropriate place. @Serge I'm kind of on vacation till next week :) I might create a PPA with a suggested fix on Monday. -- Ante Karamatic ante.karama...@canonical.com Professional and Engineering Services Canonical Ltd -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
I think we removed that 'incompatible' message upstream earlier this year, so you might want to look at a more recent upstream version. Alasdair -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Found several miss-spellings of globally_unique, in the following files; /usr/lib/ocf/resource.d/lvm2/clvmd /usr/lib/ocf/resource.d/pacemaker/controld /usr/lib/ocf/resource.d/pacemaker/o2cb Now testing ... -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Testing the correction of spelling was not a success. Although Ante thank you for your suggestion about /usr/lib/ocf/resource.d/lvm2/clvmd the VG's are not brought online in that, although it did help me to see /usr/lib/ocf/resource.d/heartbeat/LVM trying the --monitor y fix to that now. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
The hack of /usr/lib/ocf/resource.d/heartbeat/LVM has tested successfully. The spelling fixes are also still in place, so I don't know if either one was the magic bullet or if it was both. Thanks for your assistance Ante Hope this helps other too. -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
On Thu, Nov 22, 2012 at 05:10:25PM -, Robert McGrath wrote: The spelling fixes are also still in place, I notified upstream: https://github.com/beekhof/pacemaker/commit/932e41e Alasdair -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
ivoks or xnox, are you still working on this bug? (I just instrumented toollib.c and it sure seems like, in raring, monitoring is being correctly set based on lvm.conf, but I probably don't have things set up right) -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Let's take this last hurdle to have fully working cluster support under Ubuntu! -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Since this is released in .96, this should probably be released in Quantal first, as this bug affects all releases, not just 12.04. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Debian Wheezy has 2.02.95-4, seems like a good starting point for a new ubuntu package ;) -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
2.02.95-4 seems to have the same monitoring-default-off.patch as we can find in the Ubuntu packages. Does this mean it's an issue for Debian ( wheezy ) as well? -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Since this is blocking the deploy of my new Ubuntu 12.04 based environment, how should i proceed, roll my own deb with the latest lvm2 version, or is there something i can do to help this along? I would prefer this to be fixed in the official LTS release instead of having to maintain my own debs though, so just yell! -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Ok, so what's the plan of action here? Backport the fix? -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
The reason for the patch originally was to make sure that lvm commands by default (even without a /etc/lvm/lvm.conf) in weird/small/udeb/whatever environments do not require that dmeventd be running. It seems that the patch introduces or exposes a bug that the conf file settings aren't always (ever?) correctly read by the tools, so monitor cannot be globally enabled. This needs to be fixed. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Assigning to myself the lvm2 task to look into this for triaging. (my personal TODO list) ;-) ** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) = Dmitrijs Ledkovs (dmitrij.ledkov) -- 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
Re: [Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
This code has since changed upstream. Start here http://git.fedorahosted.org/git/?p=lvm2.git;a=commit;h=d81498a824e66acca994807643e9df1e452fd61c (dependencies on earlier commits I think too) Alasdair -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
That commit is released in 2.02.96 as far as I can see: $ git describe --contains d81498a824e66acca994807643e9df1e452fd61c v2_02_96~375 -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
So what is the way forward here? I presume adding --monitor y can't be added by default? Maybe it could be enabled through /etc/default/clvm? -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Which ofcourse still won't fix virt-manager i guess.. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Possible solution or workaround: Execute vgchange in /etc/init.d/clvm with the option --monitor y. To change /etc/init.d/clvm do: mv /etc/init.d/clvm.dist /etc/init.d/clvm sed 's/vgchange /vgchange --monitor y /g' /etc/init.d/clvm.dist /etc/init.d/clvm chmod 755 /etc/init.d/clvm -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
ITec, those packages are only for pacemaker/redhat-cluster use of cLVM - they do not fix standalone cLVM. Standalone cLVM isn't really preferred way of using clustered LVM. This is why I've marked bug in resource- agents as 'In Progress', not the one in cLVM. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Could you please add 'ppa:ivoks/ha' PPA (packages will be available in few minutes), upgrade your packages and retest? Thanks! ** Changed in: lvm2 (Ubuntu) Assignee: (unassigned) = Ante Karamatić (ivoks) ** Also affects: resource-agents (Ubuntu) Importance: Undecided Status: New ** Changed in: resource-agents (Ubuntu) Status: New = In Progress -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Note that packages in the PPA are relevant only for pacemaker and redhat-cluster clusters. ** Changed in: resource-agents (Ubuntu) Assignee: (unassigned) = Ante Karamatić (ivoks) ** Changed in: lvm2 (Ubuntu) Assignee: Ante Karamatić (ivoks) = (unassigned) -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
I have got the same problem. I installed Ante's packages from 'ppa:ivoks/ha', but the problem still consists. # lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 # dpkg -l clvm libdevmapper1.02.1 lvm2 ii clvm 2.02.66-4ubuntu7.1~ppa1 Cluster LVM Daemon for lvm2 ii libdevmapper1.02.1 2:1.02.48-4ubuntu7.1~ppa1 The Linux Kernel Device Mapper userspace library ii lvm2 2.02.66-4ubuntu7.1~ppa1 The Linux Logical Volume Manager # /etc/init.d/clvm start * Starting Cluster LVM Daemon clvm [ OK ] * Activating all VGs activation/monitoring=0 is incompatible with clustered Volume Group clvm: Skipping. 6 logical volume(s) in volume group lvm now active -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
I rebuilt the lvm2 packages from source and removed the monitoring- default-off.patch. clvm now works as expected. I believe, the patch, which defines DEFAULT_DMEVENTD_MONITOR -1 is not compatible with the location where this error occurs: toollib.c in the function get_activation_monitoring_mode. I used this patch with oneiric for a drbd/clvm/gfs/kvm cluster. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Any further news or decisions? This bug *IS* a bug. -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New = Confirmed -- 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
[Bug 833368] Re: clustered lvm commands fail with activation/monitoring=0 is incompatible with clustered Volume Group error
** Description changed:
- I'm trying to configure a clustered lvm2 using cman and clvm, but clvm
- start up and lvm commands fail with this error:
+ # lsb_release -rd
+ Description:Ubuntu 11.04
+ Release:11.04
+
+ # apt-cache policy lvm2
+ lvm2:
+ Installed: 2.02.66-4ubuntu2
+ Candidate: 2.02.66-4ubuntu2
+ Version table:
+ *** 2.02.66-4ubuntu2 0
+ 500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+ # apt-cache policy clvm
+ clvm:
+ Installed: 2.02.66-4ubuntu2
+ Candidate: 2.02.66-4ubuntu2
+ Version table:
+ *** 2.02.66-4ubuntu2 0
+ 500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+
+ # apt-cache policy libdevmapper1.02.1
+ libdevmapper1.02.1:
+ Installed: 2:1.02.48-4ubuntu2
+ Candidate: 2:1.02.48-4ubuntu2
+ Version table:
+ *** 2:1.02.48-4ubuntu2 0
+ 500 http://ubuntu.mirror.iweb.ca/ natty/main amd64 Packages
+ 100 /var/lib/dpkg/status
+
+
+
+ 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.
+ 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
+ 1 logical volume(s) in volume group data_vg now active
- activation/monitoring is set to 1.
+ 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
- }
+
+ # 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
+
