From: "Bruen, Mark" <mbruen@trilegiant.com>
To: christophe.varoqui@free.fr,
device-mapper development <dm-devel@redhat.com>
Subject: Re: /dev/dm-N and Veritas?
Date: Mon, 31 Oct 2005 15:04:08 -0500 [thread overview]
Message-ID: <436678B8.9090804@trilegiant.com> (raw)
In-Reply-To: <1130788268.13850.128.camel@zezette>
I would like to use "device mapper" for multipathing which I have setup
and Veritas Volume Manager for Virtualization. I normally create LUNs
on the SAN and they show up as /dev/sdX, /dev/sdY, etc... I initialize
them for use with Veritas Volume Manager which allows me to expand
filesystems across multiple LUNs, create snapshots, split disks off for
deporting, etc...
I have many years of Veritas experience and none with LVM so I would
(for now anyway) like to use the multipathed devices /dev/dm-N with
Veritas. Is it possible?
Thanks.
-Mark
Christophe Varoqui wrote:
>On lun, 2005-10-31 at 14:27 -0500, Bruen, Mark wrote:
>
>
>>Anyone using Veritas to manage their /dev/dm-N devices?
>>Thanks.
>>
>>
>
>I guess few people can understand what you mean.
>For one, I can't, sorry.
>
>Regards,
>cvaroqui
>
>
>
>--
>dm-devel mailing list
>dm-devel@redhat.com
>https://www.redhat.com/mailman/listinfo/dm-devel
>
>
--
Mark Bruen
mbruen@trilegiant.com
203-416-2358
What information consumes is rather obvious: it consumes the attention
of it's recipients. Hence a wealth of information creates a poverty of
attention..."
-Herbert Simon, Computer Scientist, Psychologist, Nobel Laureate
in Economics, 1978
The information in this electronic mail message is Trilegiant
Confidential and may be legally privileged. It is intended solely for
the addressee(s). Access to this Internet electronic mail message by
anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, distribution or action taken or omitted to be
taken in reliance on it is prohibited and may be unlawful.
The sender believes that this E-mail and any attachments were free of
any virus, worm, Trojan horse, and/or malicious code when sent. This
message and its attachments could have been infected during transmission.
By reading the message and opening any attachments, the recipient accepts
full responsibility for taking protective and remedial action about
viruses and other defects. Trilegiant Corporation is not liable for any
loss or damage arising in any way from this message or its attachments.
next prev parent reply other threads:[~2005-10-31 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 19:27 /dev/dm-N and Veritas? Bruen, Mark
2005-10-31 19:51 ` Christophe Varoqui
2005-10-31 20:04 ` Bruen, Mark [this message]
2005-10-31 20:30 ` Christophe Varoqui
2005-10-31 20:48 ` Bernd Zeimetz
2005-10-31 20:08 ` Greg Freemyer
2005-10-31 21:26 ` Brian Long
2005-11-01 19:04 ` Bruen, Mark
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=436678B8.9090804@trilegiant.com \
--to=mbruen@trilegiant.com \
--cc=christophe.varoqui@free.fr \
--cc=dm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.