[Ocfs2-users] OCFS2 on CentOS 4.5 for CRS/RAC

[Sunil Mushran]

When you use RAW, you are using it for only datafiles and
not binary homes. So you are not comparing apples-to-apples.

Bottomline, the fs requires a stable shared disk to work. Any
flakiness in the shared disk, and you will encounter the errors
that you are experiencing.

Anjan Chakraborty wrote:
> Mark,
> Unfortunately that's not an option. Because I am doing it for 
> non-busines/educational purpose  & I/we don't have money to go for 
> anything except FireWire. Moreover, if I use only RAW partitions of 
> that FireWire drive, everything works fine. So, it's clearly an OCFS2 
> issue. Can you please ask your enginners to look into this if they 
> have time?
> I heard many people (e.g. Jeff Hunter who wrote how to do it) have 
> implemented FireWire/OCFS2/CRS/RAC witthout any issue -- and if that 
> is the case, why wouldn't it work for us?
> Thanks for your help.
> Anjan
>
>
> */Mark Fasheh <mark.fasheh at oracle.com>/* wrote:
>
>     On Tue, Nov 27, 2007 at 11:32:52AM -0800, Anjan Chakraborty wrote:
>     > Mark,
>     > Thanks to both of you for trying to help me.
>     > I have alreaddy communicated to Luis that I have to have OCFS2
>     because my
>     > software needs Clustering technology that is absent in EXT3.
>     Moreover, both CRS
>     > & RDBMS homes should also be on shared/clustered system -- so,
>     OCFS2 is the
>     > only choice.
>     > If you can help me to understand/resolve this issue, I will
>     really appreciate
>     > that.
>     > Please note that my FireWire shared drive works perfectly when I
>     use RAW but as
>     > soon as I am trying to use OCFS2, all the problems started.
>
>     Where did you get the drivers for a shared firewire disk from? Can
>     you try
>     iscsi or aoe for your shared disk? The shared-disk firewire stuff
>     is known
>     to be flakey and was only ever intended for quick proto-typing.
>
>     Actually, a while ago one of our engineers was consistently getting
>     corruptions on every block which would change the inode signature from
>     "INODE01" to "KNODE01". Getting him off of the firewire stuff
>     solved that
>     issue (hardware and ocfs2 version stayed the same). I'd venture to
>     guess
>     that you're hitting the same type of problem.
>     --Mark
>
>     --
>     Mark Fasheh
>     Senior Software Developer, Oracle
>     mark.fasheh at oracle.com
>
>
> ------------------------------------------------------------------------
> Be a better sports nut! Let your teams follow you with Yahoo Mobile. 
> Try it now. 
> <http://us.rd.yahoo.com/evt=51731/*http://mobile.yahoo.com/sports;_ylt=At9_qDKvtAbMuh1G1SQtBI7ntAcJ> 
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ocfs2-users mailing list
> Ocfs2-users at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs2-users