@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 <
<email address hidden>> 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