public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinz.Mauelshagen@t-online.de (Heinz J . Mauelshagen)
To: christophe.varoqui@free.fr
Cc: mauelshagen@sistina.com, mge@sistina.com, linux-scsi@vger.kernel.org
Subject: Re: [lvm] [christophe.varoqui@free.fr: dm multipath target]
Date: Tue, 19 Aug 2003 18:23:47 +0200	[thread overview]
Message-ID: <20030819182347.O8420@sistina.com> (raw)
In-Reply-To: <1061299572.3f4225742287c@impt1-2.free.fr>; from christophe.varoqui@free.fr on Tue, Aug 19, 2003 at 03:26:12PM +0200

On Tue, Aug 19, 2003 at 03:26:12PM +0200, christophe.varoqui@free.fr wrote:
> > > Yes, but does it mean _your_ multipath tools will need PV UUIDs ?
> > 
> > Yes.
> > 
> You realize that it make those tools unsuitable for general use : 
> * one may not want to use the full lvm compound binary to set up multipaths
> * one may not want to tag its devices to set up multipaths, where its not necessary

The "Yes" was about the LVM2 tools and we do recommend them to be installed
to support the variaty of volume management features.

If you have a corner use case where you don't need any of them but multipath,
dmsetup can be used to cover what you want out of the box (creating ASCII
mapping tables which is simple for multipath).
No need to install LVM2 at all for that.

> 
> Shouldn't LVM2 just rely on an separate multipath management (dm-based). There
> surely will be one such implementation. We users don't need fragmentation in
> such a low-level area.

dm is the multipath runtime (through a dm multipath target).

As said: you can set up multipath configs without LVM2 in case you
don't need full volume management functionality using the dmsetup tool.
This is not the recommended way but you still can do it ;)

> 
> PS: I certainly do not disregard sistina's work on this front, and do not mean
> to be disrepectful. Just trying to forward my admin point of view.

Of course not.

> 
> regards,
> cvaroqui

-- 

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-08-19 16:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030819073926.GA423@fib011235813.fsnet.co.uk>
     [not found] ` <20030819094838.F8428@sistina.com>
2003-08-19  9:04   ` [lvm] [christophe.varoqui@free.fr: dm multipath target] christophe.varoqui
2003-08-19  9:51     ` Heinz J . Mauelshagen
2003-08-19 10:48       ` christophe.varoqui
2003-08-19 12:35         ` Heinz J . Mauelshagen
2003-08-19 13:14           ` christophe.varoqui
2003-08-19 13:26           ` christophe.varoqui
2003-08-19 16:23             ` Heinz J . Mauelshagen [this message]
2003-08-19 23:22               ` christophe varoqui
2003-08-20 13:02                 ` Heinz J . Mauelshagen
2003-08-20 14:19                   ` christophe.varoqui
2003-08-21 12:47                     ` Heinz J . Mauelshagen
2003-08-21 16:34                       ` christophe.varoqui
2003-08-22  8:51                         ` Heinz J . Mauelshagen
2003-08-22 14:59                           ` Patrick Mansfield
2003-08-22 15:34                             ` christophe.varoqui
2003-08-22 15:55                               ` Patrick Mansfield
2003-08-22 16:07                             ` christophe.varoqui
2003-08-19 14:19       ` James Bottomley
2003-08-19 16:09         ` Heinz J . Mauelshagen

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=20030819182347.O8420@sistina.com \
    --to=heinz.mauelshagen@t-online.de \
    --cc=christophe.varoqui@free.fr \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mauelshagen@sistina.com \
    --cc=mge@sistina.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