[Linux-cluster] falied to implement HA-LVM with clvmd rhcs5.6

Fri Feb 4 15:04:44 UTC 2011

Thanks.

This is the old methos and its work great but its hard to maintain such
cluster.

Shalom.

On Fri, Feb 4, 2011 at 4:32 PM, Dominic Geevarghese <share2dom at gmail.com>wrote:

>
> Hi,
>
> I am not sure about the error you are getting but it would be great if you
> could try the preferred method
>
> locking_type = 1
> volume_list [ "your-root-vg-name" , "@hostname" ]
>
> rebuild initrd
>
> add the <lvm> and <fs> resources in cluster.conf , start the cman,
> rgmanager .
>
>
> Thanks,
>
> On Thu, Feb 3, 2011 at 8:02 PM, Corey Kovacs <corey.kovacs at gmail.com>wrote:
>
>> Excellent,
>>
>>
>> Thanks
>>
>> -C
>>
>> On Thu, Feb 3, 2011 at 10:38 AM, שלום קלמר <sklemer at gmail.com> wrote:
>> >
>> >
>> > On Thu, Feb 3, 2011 at 12:35 PM, שלום קלמר <sklemer at gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> https://access.redhat.com/kb/docs/DOC-3068
>> >>
>> >> On Thu, Feb 3, 2011 at 11:13 AM, Corey Kovacs <corey.kovacs at gmail.com>
>> >> wrote:
>> >>>
>> >>> Is using ha-lvm with clvmd a new capability? It's always been my
>> >>> understanding that the lvm locking type for using ha-lvm had to be set
>> >>> to '1'.
>> >>>
>> >>> I'd much rather be using clvmd if it is the way to go. Can you point
>> >>> me to the docs you are seeing these instructions in please?
>> >>>
>> >>> As for why your config isn't working, clvmd requires that it's
>> >>> resources are indeed tagged as cluster volumes, so you might try doing
>> >>> that and see how it goes.
>> >>>
>> >>> -C
>> >>>
>> >>> On Thu, Feb 3, 2011 at 7:26 AM, שלום קלמר <sklemer at gmail.com> wrote:
>> >>> > Hello.
>> >>> >
>> >>> >
>> >>> >
>> >>> > I followed redhat instruction trying install HA-LVM with clvmd. (
>> rhcs
>> >>> > 5.6 -
>> >>> > rgmanager 2.0.52-9 )
>> >>> >
>> >>> >
>> >>> >
>> >>> > I can't make it work.
>> >>> >
>> >>> >
>> >>> >
>> >>> > lvm.conf- locking_type=3
>> >>> >
>> >>> > clvmd work
>> >>> >
>> >>> > Its failed saying HA-LVM is not configured correctly.
>> >>> >
>> >>> > The manual said that we should run "lvchange -a n lvxx" edit the
>> >>> > cluster.conf & start the service.
>> >>> >
>> >>> >
>> >>> >
>> >>> > But From lvm.conf :
>> >>> >
>> >>> >
>> >>> >
>> >>> > case $1 in
>> >>> >
>> >>> > start)
>> >>> >
>> >>> >         if ! [[ $(vgs -o attr --noheadings $OCF_RESKEY_vg_name) =~
>> >>> > .....c
>> >>> > ]]; then
>> >>> >
>> >>> >                 ha_lvm_proper_setup_check || exit 1
>> >>> >
>> >>> >
>> >>> >
>> >>> > If the vg is not taged as cluster than the ha_lvm is looking for
>> >>> > volume_list
>> >>> > in lvm.conf.
>> >>> >
>> >>> >
>> >>> >
>> >>> > I am confused- Does the VG should taged as cluster ??  ( BTW - the
>> old
>> >>> > fashion HA-LVM is worked with no problems )
>> >>> >
>> >>> > redhat instructions :
>> >>> >
>> >>> > To set up HA LVM Failover (using the preferred CLVM variant),
>> perform
>> >>> > the
>> >>> > following steps:
>> >>> >
>> >>> >
>> >>> >
>> >>> > 1. Ensure that the parameter locking_type in the global section
>> >>> > of /etc/lvm/lvm.conf is set to the value '3', that all the necessary
>> >>> > LVM
>> >>> > cluster packages are installed, and the necessary daemons are
>> started
>> >>> > (like
>> >>> > 'clvmd' and the cluster mirror log daemon - if necessary).
>> >>> >
>> >>> >
>> >>> >
>> >>> > 2. Create the logical volume and filesystem using standard LVM2 and
>> >>> > file
>> >>> > system commands. For example:
>> >>> >
>> >>> > # pvcreate /dev/sd[cde]1
>> >>> >
>> >>> >  # vgcreate <volume group name> /dev/sd[cde]1
>> >>> >
>> >>> >  # lvcreate -L 10G -n <logical volume name> <volume group name>
>> >>> >
>> >>> >  # mkfs.ext3 /dev/<volume group name>/<logical volume name>
>> >>> >
>> >>> >  # lvchange -an <volume group name>/<logical volume name>
>> >>> >
>> >>> >
>> >>> >
>> >>> > 3. Edit /etc/cluster/cluster.conf to include the newly created
>> logical
>> >>> > volume as a resource in one of your services. Alternatively,
>> >>> > configuration
>> >>> > tools such as Conga or system-config-cluster may be used to create
>> >>> > these
>> >>> > entries.  Below is a sample resource manager section
>> >>> > from /etc/cluster/cluster.conf:
>> >>> >
>> >>> >
>> >>> >
>> >>> > <rm>      <failoverdomains>        <failoverdomain name="FD"
>> >>> > ordered="1"
>> >>> > restricted="0">           <failoverdomainnode name="neo-01"
>> >>> > priority="1"/>
>> >>> >           <failoverdomainnode name="neo-02" priority="2"/>
>> >>> > </failoverdomain>    </failoverdomains>    <resources>        <lvm
>> >>> > name="lvm" vg_name="shared_vg" lv_name="ha-lv"/>        <fs
>> name="FS"
>> >>> > device="/dev/shared_vg/ha-lv" force_fsck="0" force_unmount="1"
>> >>> > fsid="64050"
>> >>> > fstype="ext3" mountpoint="/mnt" options="" self_fence="0"/>
>> >>> > </resources>
>> >>> >    <service autostart="1" domain="FD" name="serv"
>> recovery="relocate">
>> >>> >        <lvm ref="lvm"/>        <fs ref="FS"/>    </service> </rm>
>> >>> >
>> >>> >
>> >>> >
>> >>> > Regards
>> >>> >
>> >>> > Shalom.
>> >>> >
>> >>> >
>> >>> >
>> >>> > --
>> >>> > Linux-cluster mailing list
>> >>> > Linux-cluster at redhat.com
>> >>> > https://www.redhat.com/mailman/listinfo/linux-cluster
>> >>> >
>> >>>
>> >>> --
>> >>> Linux-cluster mailing list
>> >>> Linux-cluster at redhat.com
>> >>> https://www.redhat.com/mailman/listinfo/linux-cluster
>> >
>> >
>> > --
>> > Linux-cluster mailing list
>> > Linux-cluster at redhat.com
>> > https://www.redhat.com/mailman/listinfo/linux-cluster
>> >
>>
>> --
>> Linux-cluster mailing list
>> Linux-cluster at redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-cluster
>>
>
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20110204/12b67693/attachment.htm>