From: "J. Ryan Earl" <ryan@dynaconnections.com>
To: Lars Marowsky-Bree <lmb@suse.de>, miele@inwind.it
Cc: jakob <jakob@unthought.net>,
linux-raid <linux-raid@vger.kernel.org>,
mingo <mingo@chiara.csoma.elte.hu>, bueso <bueso@vives.org>
Subject: RE: Can you help me on Linux SW RAID?
Date: Thu, 28 Apr 2005 14:18:28 -0500 [thread overview]
Message-ID: <OMEKLMBKKEOEENCKLEIDAEPDCIAA.ryan@dynaconnections.com> (raw)
In-Reply-To: <20050428130633.GT21645@marowsky-bree.de>
OCFS2 isn't stable yet, I wouldn't suggest its use for production systems.
Furthermore, where did the requirement for 2.6 (kernel I assume) come from?
Sounds like he was using RHEL3 anyway...
I'm not familar with the 9i RAC setup, but I installed a 10g RAC that's in
production now. The only thing I use OCFS for is Cluster Registry, Disk
Voting, and the Oracle Parameter File. All database nodes have access to
the same set of raw LUNs on the SAN managed via ASM (Automated Storage
Management, a 10g feature) for keeping actual data on. You could just put
all your Oracle files/data on OCFS, but that's not the highest performance
solution.
To have multiple nodes access a non-Oracle data on a clustered filesystem,
go with GFS for sure, ie a normal POSIX complaint filesystem. OCFSv1 isn't
POSIX complaint and only properly stores Oracle specific files, and though
OCFSv2 is meant to be a generic clustered filesystem, it's not production
ready like I mentioned before: http://oss.oracle.com/projects/ocfs2/
How you setup the RAID is completely different issue from how you cluster
your data among nodes.
-ryan
-----Original Message-----
From: linux-raid-owner@vger.kernel.org
[mailto:linux-raid-owner@vger.kernel.org]On Behalf Of Lars Marowsky-Bree
Sent: Thursday, April 28, 2005 8:07 AM
To: miele@inwind.it
Cc: jakob; linux-raid; mingo; bueso
Subject: Re: Can you help me on Linux SW RAID?
On 2005-04-28T14:57:29, "miele@inwind.it" <miele@inwind.it> wrote:
> Have you experienced problem using OCFS insetad of OCFS2??
OCFS isn't available on 2.6. On 2.6, you have to use OCFS2.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
-
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
-
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:[~2005-04-28 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 12:57 Can you help me on Linux SW RAID? miele
2005-04-28 13:06 ` Lars Marowsky-Bree
2005-04-28 19:18 ` J. Ryan Earl [this message]
2005-04-28 19:56 ` Lars Marowsky-Bree
2005-04-28 22:32 ` Can you help me on Linux SW RAID? [OT] J. Ryan Earl
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 11:41 Can you help me on Linux SW RAID? miele
2005-04-28 11:49 ` Lars Marowsky-Bree
2005-04-28 10:27 miele
2005-04-28 10:11 miele
2005-04-28 11:29 ` Jakob Oestergaard
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=OMEKLMBKKEOEENCKLEIDAEPDCIAA.ryan@dynaconnections.com \
--to=ryan@dynaconnections.com \
--cc=bueso@vives.org \
--cc=jakob@unthought.net \
--cc=linux-raid@vger.kernel.org \
--cc=lmb@suse.de \
--cc=miele@inwind.it \
--cc=mingo@chiara.csoma.elte.hu \
/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).