From: German Staltari <gstaltari@arnet.net.ar>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] gfs with multipath
Date: Tue, 28 Mar 2006 20:15:42 -0300 [thread overview]
Message-ID: <4429C39E.4040406@arnet.net.ar> (raw)
Hi, It's possible to do a multipath device with devices that are part of
a already created gfs filesystem without losing data? If the question
it's not clear here is a detailed explanation:
I have created a gfs filesystem (the usual procedure) that has two paths
to the same device (QLogic hba connected to an IBM SAN)
Example: /dev/sdb is the same as /dev/sdc and my PV was created with
/dev/sdc.
Now I would like to create a multipath device with this devices
(/dev/sdb and /dev/sdc) but I don't want to lose my data. Is that possible?
FC4
kernel-smp-2.6.15-1.1831_FC4
device-mapper-multipath-0.4.4-2.3
LVM version: 2.01.08 (2005-03-22)
Library version: 1.01.02 (2005-05-17)
Driver version: 4.4.0
Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 02)
My question is related to my previous post:
https://www.redhat.com/archives/linux-lvm/2006-March/msg00051.html
Thanks
German Staltari
reply other threads:[~2006-03-28 23:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4429C39E.4040406@arnet.net.ar \
--to=gstaltari@arnet.net.ar \
--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).