From: Matt Domsch <Matt_Domsch@dell.com>
To: "pg@atlavia.it" <pg@atlavia.it>
Cc: linux-scsi@vger.kernel.org
Subject: Re: megaraid Error 40005 on cluster
Date: Thu, 19 May 2005 09:23:55 -0500 [thread overview]
Message-ID: <20050519142355.GA2261@lists.us.dell.com> (raw)
In-Reply-To: <151.92.176.3.1249009224.1116511903@webmail.atlavia.it>
On Thu, May 19, 2005 at 02:11:43PM +0000, pg@atlavia.it wrote:
> I exerienced the following error on a RedHat cluster configuration
> with Dell hardware (Perc 3/DC controller and PowerVault 220 disk
> array). When the error occurs the cluster manager shutdown the
> cluster node, but the filesystem is corruped and the other node
> cannot mount it until a manual fsck.
>
> Any idea?
The firmware on the PERC 3/DC is not multi-initiator cluster-capable
under Linux. For this reason, neither Dell nor Red Hat recommend
trying to create a HA shared storage cluster with this configuration.
Even with write cache disabled, the lock sectors used by the cluster
manager don't manage to stay coherent.
I understand that newest versions of the Red Hat Cluster Suite may no
longer use lock sectors on the disk as the I/O fencing mechanism,
which may then enable such configurations. But neither Dell nor Red
Hat have done any testing with the hardware config you've got.
The price is right, until you actually need your data to be highly
available and it crashes.
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2005-05-19 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 14:11 megaraid Error 40005 on cluster pg
2005-05-19 14:23 ` Matt Domsch [this message]
2005-05-19 19:39 ` Pg
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=20050519142355.GA2261@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=pg@atlavia.it \
/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