From: Garrick Staples <garrick@usc.edu>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] HA Fileserver configuration recommendation sought.
Date: Fri, 19 Nov 2004 10:24:14 -0800 [thread overview]
Message-ID: <20041119182414.GF3139@polop.usc.edu> (raw)
In-Reply-To: <1100885267.19894.217.camel@rct07.cadence.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
On Fri, Nov 19, 2004 at 09:27:47AM -0800, Chris Croswhite alleged:
> I use the ATABoy 2x (dual active/active FC) with great success. I use
> md to create a failover path (see mdadm) on newer kernels (2.6.9) and I
> have multiple 3.2T LUNS (multiple ataboys). I use LVM2 to partition
> some of the LUNs with great success.
How do you solve the problem of lvm2 seeing 3 duplicate PVs (2 paths and 1 md
device)? Are you using the filter in /etc/lvm/lvm.conf?
--
Garrick Staples, Linux/HPCC Administrator
University of Southern California
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-11-19 18:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 9:47 [linux-lvm] HA Fileserver configuration recommendation sought Gary Mansell
2004-11-19 17:27 ` Chris Croswhite
2004-11-19 18:24 ` Garrick Staples [this message]
2004-11-19 18:30 ` Chris Croswhite
2004-11-19 19:45 ` David S.
2004-11-19 18:21 ` Dan Stromberg
2004-11-19 19:24 ` David S.
2004-11-20 0:13 ` Dan Stromberg
2004-11-20 0:22 ` Garrick Staples
2004-11-20 1:36 ` Dan Stromberg
2004-11-20 2:08 ` Garrick Staples
2004-11-20 2:18 ` Dan Stromberg
2004-11-20 2:48 ` David Aquilina
2004-11-22 15:36 ` Kevin Anderson
2004-11-23 0:42 ` Dan Stromberg
2004-11-23 2:10 ` [linux-lvm] Re: lvextend error on XFS Frank J. Buchholz
2004-11-23 8:38 ` David Greaves
2004-11-23 12:37 ` Frank J. Buchholz
2004-11-20 0:33 ` [linux-lvm] HA Fileserver configuration recommendation sought David S.
2004-11-20 1:40 ` Dan Stromberg
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 20:07 Shea,Dan [CIS]
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=20041119182414.GF3139@polop.usc.edu \
--to=garrick@usc.edu \
--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