From: Steven Dake <sdake@mvista.com>
To: frank@behner.org
Cc: linux-raid@vger.kernel.org
Subject: Re: HA with qlogic FC and linux raid
Date: Mon, 20 Jan 2003 12:17:27 -0700 [thread overview]
Message-ID: <3E2C4B47.2090004@mvista.com> (raw)
In-Reply-To: <1042980305.3e2a9dd18c42a@secure.private.behner.org>
Do you see an OOPS when one of the paths of the multipath leaves, or
only when all paths are dead or in LIP.
Thanks
-steve
frank@behner.org wrote:
>Hi,
>
>We try to build a HA environment for a Document Management System. Before I come
>to the problem I will briefly describe our setup. We have two buildings and a
>fibrechannel switch in each building and attached to it a disk arrays, a DB
>server for the metadata (Linux with Oracle) and a fileserver under W2K for the
>bulk data. The fileserver runs under W2K, because the application server runs
>under W2K. The servers are also connected to the switch in the other building.
>The idea is to mirror the data over the buildings. All machines are connected
>with two fibres (using QLA2202F cards) to each switch. Also the arrays are using
>two connections to the switch. is true for. So we have a multiple pathes from
>the machines to the arrays.
>
>The Linux machines are using md-raidtools to mirror over the buildings. To see
>the correct number of devices we have used first the failover qlogic driver 6.01
>and afterwards the standard version upto 6.04beta4 with the multipath
>personality of the mdtools.
>
>The system runs till we need the failover. But if pathes are not available we
>get a kernel Oops in the RAID1 personality of the md and any IO to the disk
>arrays hangs forever, the machine does also not shutdown correctly. Because we
>see this behaviour also if a windows machine boots and sends a LIP reset over
>the fibre channel, this is even for normal operations not acceptable. Needless
>to say that the W2K do not have this problem. Therefore we concluded that the
>setup of the hardware is ok,(BIOS settings are the same for Linux and W2K). Of
>course we are unsure whether the problem is in the mdtools or in the qlogic
>driver (who should handle the LIP reset). We try to get help from Linux
>companies, but we where not very successful.I could send the list Oops and more
>information if it would help. Maybe it is well known problem having a raid1
>personality over two multipath personalities. (The Oops says something from a
>NULL pointer which he can't follow and if I understood it correctly, it happens
>after all pathes are gone, due to LIP reset). The LIP reset problem was first
>seen while the mirror was resyncing and a windows machine got rebooted.
>
>Thank you for some feedback
> Frank Behner
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
>
next prev parent reply other threads:[~2003-01-20 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-19 12:45 HA with qlogic FC and linux raid frank
2003-01-20 19:17 ` Steven Dake [this message]
2003-01-20 22:13 ` Frank Behner
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=3E2C4B47.2090004@mvista.com \
--to=sdake@mvista.com \
--cc=frank@behner.org \
--cc=linux-raid@vger.kernel.org \
/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.