<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1498" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I did an experiment, using OCFSv2 as a doicument
storage in development lab (doc storage is for the users of the product, not for
developers, so we could tes - it had about 20 - 30 GB of small files and had a
concurrent access from 2 servers).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Results:</FONT></DIV>
<DIV><FONT face=Arial size=2>- cluster died 2 times in 2 weeks (each time at
night, by some reason).</FONT></DIV>
<DIV><FONT face=Arial size=2>- first failure resulted in totally damaged system
disk on node-2 </FONT></DIV>
<DIV><FONT face=Arial size=2>- in both failures, 1 node (it runs SMP kernel)
freeze, and second node died in a few hours. </FONT></DIV>
<DIV><FONT face=Arial size=2>- after second failure, 1 directory had a bad file
counter.</FONT></DIV>
<DIV><FONT face=Arial size=2>- no data loss in 2 weeks. </FONT></DIV>
<DIV><FONT face=Arial size=2>- performance is good except some moments, when
o2net spent 30 - 50% of all CPU power;</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Most annoying things are:</FONT></DIV>
<DIV><FONT face=Arial size=2>- self-fencing. First of all, SLES9 have _dont
reboot on panic_ default, so fencing just _freeze_ server.</FONT></DIV>
<DIV><FONT face=Arial size=2> problem is that in 90% cases there was
not any activity on file system, so it could just _remount_. </FONT></DIV>
<DIV><FONT face=Arial size=2> Other problem is that in many cases, I
prefer to LOCK file system but dont reboot (example - OCFS2 used</FONT></DIV>
<DIV><FONT face=Arial size=2> to store Oracle backups).</FONT></DIV>
<DIV><FONT face=Arial size=2> </FONT></DIV>
<DIV><FONT face=Arial size=2> Second - I have many servers around.
I'd like to show few of them as _arbiters for OCFSv2_. But I dont like them to
reboot</FONT></DIV>
<DIV><FONT face=Arial size=2> in any case, and I do not need to
mount file system on them.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> </FONT></DIV>
<DIV><FONT face=Arial size=2>- heartbeat. I use 2 ethernets + serial in Linux
cluster; use 4 ethernets in PIX cluster, use 3 ethernet in Veritas cluster. Why
OCFSv2 is</FONT></DIV>
<DIV><FONT face=Arial size=2> so dumb that I cannot configure few IP for
the server? It makes system very unstable (and if you remember about _self
fencing_ - </FONT></DIV>
<DIV><FONT face=Arial size=2> makes it unusable).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>- symlink errors are reported into syslog - hmm,
what an excellent idea -:). Why dont report any syscall error into the syslog
(dont forget to purchase separate 200 GB disk before doing it).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>So. It looks good, after old and broken
implememntations. But it (still) do not work. And in many cases, it decrease
reliability instead of increaing it (senf fencing of oracle backup file system
is a good example).</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Any ideas - may be, kernel 257 had a broiken
version? In one case, I find root file system broken, and it looked as OCFSv2
wrote wrong buffers.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV></BODY></HTML>