linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "C'est Pierre" <cestpierre@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: alternate link / multi-pathing
Date: Sun, 28 May 2006 15:35:38 +0100	[thread overview]
Message-ID: <5485940d0605280735j4aba6709qb601484cd457452e@mail.gmail.com> (raw)
In-Reply-To: <20060528091024.GY8203@percy.comedia.it>

Hello Luca,

Thanks for pointing me that out, too bad it's a bit late, since the
server is now crashed and only tomorrow I will be able to reset it.
Meanwhile, I've got a few questions for you:

1. How do I disable raid autodetect ?
2. Where can I read about device-mapper-multipath ?
3. To deactivate the vg, I suppose I should use vgchange -a n, correct
me if I am wrong

Thank you for your reply!
Gon�alo


On 5/28/06, Luca Berra <bluca@comedia.it> wrote:
> On Sun, May 28, 2006 at 02:50:24AM +0100, C'est Pierre wrote:
> >Nevermind about my previous question! I just made my way into this
> >page:
> >http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/s390-multi-install-guide/s1-s390info-raid.html
> >and have setup the multipathing nicely.
>
> actually the device-mapper-multipath would a better approach than
> md-multipath
>
> >However, I went into the second node (this is 2 nodes failover cluster
> >environment) and I noticed that the vg and the md0 appeared there
> >there automatically! is this normal? is there anything I should do?
>
> it is not normal
> it should not happen
>
> if you insist in using md multipath, ensure raid autodetect won't pick
> it up.
> i.e. disable damned autodetect on kernel command line or
> change the partition type to something different than 'Linux Raid'
>
> then you'll have to ensure that your distribution  init scripts do not
> automatically start it.
> best way is omitting this set entries from /etc/mdadm.conf
> and putting it somewhere else, then invoking
> "mdadm -Asc /some/where/else/mdadm.conf" in your cluster script
>
> if you use device-mapper-multipath (which might also solve the issue in
> your next post :)
> there is no problem if multipath finds the devices on the failover node,
> but you must prevent lvm from activating the vg
>
> to do this either add cluster locking or use tags, as explained in the
> doc/tagging.txt files in the lvm distribution
>
> Regards,
> L.
>
>
> --
> Luca Berra -- bluca@comedia.it
>         Communication Media & Services S.r.l.
>  /"\
>  \ /     ASCII RIBBON CAMPAIGN
>   X        AGAINST HTML MAIL
>  / \
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

  reply	other threads:[~2006-05-28 15:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-28  0:11 [linux-lvm] alternate link / multi-pathing C'est Pierre
2006-05-28  1:50 ` [linux-lvm] " C'est Pierre
2006-05-28  9:10   ` Luca Berra
2006-05-28 14:35     ` C'est Pierre [this message]
2006-05-28 15:50       ` Luca Berra
2006-05-28  2:00 ` C'est Pierre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5485940d0605280735j4aba6709qb601484cd457452e@mail.gmail.com \
    --to=cestpierre@gmail.com \
    --cc=linux-lvm@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).