From: Ritesh Raj Sarraf <rrs@researchut.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM + Multipath
Date: Mon, 19 Feb 2007 18:33:50 +0530 [thread overview]
Message-ID: <mqjoa4-2hn.ln1@www.researchut.com> (raw)
Hi,
I have a question regarding the combination of LVM + Multipathing in a SAN
environment.
I have a LUN mapped to a host using iSCSI. I have two two paths to the LUN. This
setup, using multipathing, provides me failover functionality.
My question is how does LVM react to path failures ?
In a failover environment, multipathing can take upto 120 seconds to detect that
the active path to the LUN is no more available and then switch to the
secondary path. During this 120 seconds, how does LVM react ? Does it really
sense that the device is offlined ? Or that information is never passed to LVM
and it just allows I/O to happen leaving that responsibility to the
multipathing layer ?
Thanks,
Ritesh
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
"Stealing logic from one person is plagiarism, stealing from many is research."
"The great are those who achieve the impossible, the petty are those who
cannot - rrs"
reply other threads:[~2007-02-19 13:30 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=mqjoa4-2hn.ln1@www.researchut.com \
--to=rrs@researchut.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).