Alexei_Roudnev wrote:

>No, high load was by Oracle ASM, not by OCFSv2.
>
>Here is the problem - after upgrading to Oracle 10.2.0.2 (which I guess I
>should not do next time, because 10.2.0.2. looks broken in a few minor
>places and it indicates bad testing as usual), when I run high load tests on
>Oracle (with moderate or low load on OCFSv2), it cause OCFSv2 instability.
>
>

  Based on my own experiences I can't help but think that
iSCSI is more of a problem here than OCFS2 is. Now I agree
that OCFS2 isn't quite up to snuff as an HA solution yet but
it seems robust enough if your interest is primarily in being
able to scale to many cpus cheaply.

>Reading documentation and sources make me conclude that OCFSv2 cannot be
>used in current conditions at all, even if I saw a bug, not normal behavior
>(there is some indication that there was such bug in OCFS 1.18). Adding OCFS
>into Oracle RAC environment increases a chances to sporadic system reboots
>(because of clueless fencing in OCFSv2), and so can make the whole cluster
>useless or damage files (I had already damaged udev cache because of these
>reboots).
>
>Moreover, after a few fencings I run full ocfsv2 fsck and find few
>inconsistencies /fixing them did not helped with fencing, btw/. In some
>point, failed cluster caused third server (which I used as a passive mounter
>to maintain a quorum) to experience a kernel error (and stick on OCFSv2
>forever). So, it all together increase instability in thousands time.
>
>
>
  I'll have to play with this and see what happens with
my configuration.



--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting