[Linux-cluster] HA-LVM and /etc/lvm/lvm.conf

[emmanuel segura]

HA-LVM it's deprecated on redhat cluster

2012/2/2 jose nuno neto <jose.neto at liber4e.com>

> Hi
>
> I have used LVM-HA on a previous project and for Failover Cluster works
> fine.
> Didn't use DRBD with it, have tested DRBD for concurrent access to
> devices/filesystems
>
> For volume_list I would use something like this
> "@rhel-01"
> if you put
> "@*"
> think it will allow all tags
> so guess you should remove it
>
> anyway, didn't fully understand the DRDB here, you provide this LVM-HA has
> DRBD resources? If so you dont need LVM tags for this. just normal LVM
> LVM tags in redhat cluster are used to allow switching access to the Vgs
> from one node to others
>
> Regards
> Jose
>
> > I'm having a dialog with RH support about configuring HA-LVM within RHCS
> > and I'm trying to see if there are some limitations and thought I'd ping
> > the mailing list on the same subject.
> >
> > Is an HA-LVM configuration that only uses LVM tags useful beyond a single
> > volume group?
> >
> > I'm attempting to provide a database service along side a pair of HA-NFS
> > services that utilize DRBD and LVM (but drbd isn't the issue).
> >
> > on two nodes, rhel-01 and rhel-02, I currently I have three volume
> groups:
> >  vgTest0, vgTest1, vgTestCluster
> >
> > vgTest0 and vgTest1 are volume groups that exist on each node, and they
> > provide a single back-end LVM volume to a DRBD resource, so DRBD can
> > leverage the snapshotting technique  during syncs.  Both nodes in the
> > cluster have the same configuration, and DRBD is working fine.  This has
> > been in production for about a month.
> >
> > I recently got the SAN resource that is presented to both hosts that I
> > want to roll in LVM so I can utilize snapshots on the volume data.  I
> > don't want to bother with CLVM because I have a use case for
> snapshotting,
> > so HA-LVM as described: https://access.redhat.com/kb/docs/DOC-3068, I'm
> > doing the second method.  The goal is a failover cluster.
> >
> > I've been struggling with how to configure my /etc/lvm/lvm.conf because
> of
> > the volume_list parameter:
> >
> >
> > # If volume_list is defined, each LV is only activated if there is a
> > # match against the list.
> > #   "vgname" and "vgname/lvname" are matched exactly.
> > #   "@tag" matches any tag set in the LV or VG.
> > #   "@*" matches if any tag defined on the host is also set in the LV or
> > VG
> > #
> > # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
> >
> > would I go with something like:
> > volume_list = [ "vgTest0", "vgTestCluster/lvTest0", "@rhel-01", "@*" ]
> >
> > I don't get why I need to state a persistent volume group - and if I do,
> > which one?  I've got two persistent groups on each node.  I don't use LVM
> > on the root disk.
> >
> > Could I somehow expand this out to two HA-LVM volume groups? I don't see
> a
> > way but thought I'd ask.
> >
> >
> >
> > Erik Redding
> > Systems Programmer, RHCE
> > Core Systems
> > Texas State University-San Marcos
> >
> >
> > --
> > Linux-cluster mailing list
> > Linux-cluster at redhat.com
> > https://www.redhat.com/mailman/listinfo/linux-cluster
> >
> > --
> > This message has been scanned for viruses and
> > dangerous content by MailScanner, and is
> > believed to be clean.
> >
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster
>



-- 
esta es mi vida e me la vivo hasta que dios quiera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20120202/c7d533e5/attachment.htm>