Thanks a bunch for the reply, which could give me some inside view
without going through the code. It'd have been great, if you had
written a doc mentioning all these details and rolled it out :)<br><br>
There are some ocfs2_wq, ocfs2_vote and ocfs2_cmt threads created, when I mount a shared volume. Any details about them?<br>
<br>
Moreover, as you said that OCFS2 has shorter timings than that of CRS,
so do we solely depend on this fact (shorter timings) to prevent CRS
from intruding into racing during crash and split-brain situations. I
was just trying to understand how it works. I think CRS misscount is 60
for Linux. Do we believe that by this time, OCFS2 would have taken all
the decisions and completed the recovery before CRS (or rather CSSD)
starts its ejection mechanism? Without ASM, how do we ensure that
underlying Volume Manager's recovery has been completed before OCFS2
starts its recovery. And how does it happen when we use ASM?<br>
<br>
Sorry, if I am going out of the context, but just wanted to get some information how they co-ordinate.<br>
<br>
Thanks.<br>
Sumsha.<br><div><span class="gmail_quote">On 5/2/06, <b class="gmail_sendername">Sunil Mushran</b> <<a href="mailto:Sunil.Mushran@oracle.com">Sunil.Mushran@oracle.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The modules don't map one on one. The idea is to keep the<br>number of modules at a minimum while retaining some sense<br>modularity.<br><br>For e.g., ocfs2_nodemanager.ko encompasses nm, heartbeat and net/tcp.<br><br>The various kernel/worker threads may change over time.
<br>For e.g., we added dlm_wq in the last drop. Again, the idea is to<br>keep the threads at a minimum while still functioning. :)<br><br>o2cb (ocfs2 cluster stack) and crs have nothing in common. No, they<br>don't talk to each other. o2cb is almost entirely implemented in kernel
<br>space while crs in userspace.<br><br>ocfs2 default timings are much shorter than crs. The idea is to recover<br>dead nodes before crs times out.<br><br>Sum Sha wrote:<br>> Thanks Sunil for this information. I tried going through the docs
<br>> mentioned there, they are useful, but there are details which I wanted<br>> for my learning purpose which are not in those docs. It would be<br>> great if anyone can share any good doc mentioning details about
<br>> Clustering Services which OCFS2 uses. I know that clustering services<br>> which OCFS2 uses has the following components:<br>><br>> 1. Node manager<br>> 2. Heartbeat module<br>> 3. TCP Protocol module
<br>> 4. DLM<br>><br>> But once I install and configure OCFS2, I can see the following<br>> modules getting loaded:<br>><br>> 1. configfs (with filesystem mounted)<br>> 2. ocfs2_nodemanger<br>> 3. ocfs2_dlm
<br>> 4. ocfs2_dlmfs (with filesystem mounted)<br>><br>> and the following threads created:<br>> 1. ocfs2_wq (perhaps it's the kernel worker thread)<br>> 2. ocfs2_vote (for voting requests. Is this the listener thread?)
<br>> 3. ocfs2_cmt (perhaps this is the node monitoring thread?)<br>><br>> Can't think of OCFS2 in 10g environment where we have another required<br>> and reliable clustering service CRS (with 10g) running and managing
<br>> Oracle's resources. Do CRS and OCFS's clustering services co-ordinate<br>> in some manner or do they take actions independently on their own<br>> during crash and other conditions?<br>><br>> Any help would be highly appreciated!!
<br>><br>> Thanks.<br>> Sumsha.<br>><br>> On 4/28/06, *<a href="mailto:ocfs2-devel-request@oss.oracle.com">ocfs2-devel-request@oss.oracle.com</a><br>> <mailto:<a href="mailto:ocfs2-devel-request@oss.oracle.com">
ocfs2-devel-request@oss.oracle.com</a>>* <<br>> <a href="mailto:ocfs2-devel-request@oss.oracle.com">ocfs2-devel-request@oss.oracle.com</a><br>> <mailto:<a href="mailto:ocfs2-devel-request@oss.oracle.com">ocfs2-devel-request@oss.oracle.com
</a>>> wrote:<br>><br>> Send Ocfs2-devel mailing list submissions to<br>>
<a href="mailto:ocfs2-devel@oss.oracle.com">ocfs2-devel@oss.oracle.com</a> <mailto:<a href="mailto:ocfs2-devel@oss.oracle.com">ocfs2-devel@oss.oracle.com</a>><br>><br>> To subscribe or unsubscribe via the World Wide Web, visit
<br>> <a href="http://oss.oracle.com/mailman/listinfo/ocfs2-devel">http://oss.oracle.com/mailman/listinfo/ocfs2-devel</a><br>> or, via email, send a message with subject or body 'help' to<br>>
<a href="mailto:ocfs2-devel-request@oss.oracle.com">ocfs2-devel-request@oss.oracle.com</a><br>> <mailto:<a href="mailto:ocfs2-devel-request@oss.oracle.com">ocfs2-devel-request@oss.oracle.com</a>><br>><br>> You can reach the person managing the list at
<br>> <a href="mailto:ocfs2-devel-owner@oss.oracle.com">ocfs2-devel-owner@oss.oracle.com</a><br>> <mailto:<a href="mailto:ocfs2-devel-owner@oss.oracle.com">ocfs2-devel-owner@oss.oracle.com</a>>
<br>><br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Ocfs2-devel digest..."<br>><br>><br>> Today's Topics:<br>><br>> 1. Re: Please help me in getting OCFS2 design doc. (Sunil Mushran)
<br>><br>><br>> ----------------------------------------------------------------------<br>><br>><br>> Message: 1<br>> Date: Thu, 27 Apr 2006 10:03:23 -0700<br>> From: Sunil Mushran <
<a href="mailto:Sunil.Mushran@oracle.com">Sunil.Mushran@oracle.com</a><br>> <mailto:<a href="mailto:Sunil.Mushran@oracle.com">Sunil.Mushran@oracle.com</a>>><br>> Subject: Re: [Ocfs2-devel] Please help me in getting OCFS2 design
<br>> doc.<br>> To: Sum Sha <<a href="mailto:sumsha.matrixreloaded@gmail.com">sumsha.matrixreloaded@gmail.com</a><br>> <mailto:<a href="mailto:sumsha.matrixreloaded@gmail.com">sumsha.matrixreloaded@gmail.com
</a>>><br>> Cc: <a href="mailto:ocfs2-devel@oss.oracle.com">ocfs2-devel@oss.oracle.com</a> <mailto:<a href="mailto:ocfs2-devel@oss.oracle.com">ocfs2-devel@oss.oracle.com</a>><br>> Message-ID: <
<a href="mailto:4450F95B.8000704@oracle.com">4450F95B.8000704@oracle.com</a><br>> <mailto:<a href="mailto:4450F95B.8000704@oracle.com">4450F95B.8000704@oracle.com</a>>><br>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
<br>><br>> Look into docs in ocfs2 projects page. While there<br>> is no design doc, there is a presentation which lists<br>> out the changes.<br>><br>> <a href="http://oss.oracle.com/projects/ocfs2/documentation/">
http://oss.oracle.com/projects/ocfs2/documentation/</a><br>><br>> Sum Sha wrote:<br>> > Hi all,<br>> > Could someone point me to design doc for OCFS2? I could get OCFS<br>> V-1<br>> > design doc, but could not find any design doc for OCFS2. I read
<br>> > somewhere that OCFS2 has got lots of design changes as comapared to<br>> > OCFS1.<br>> ><br>> > Thanks in advance.<br>> ><br>> > _______________________________________________
<br>> > Ocfs2-devel mailing list<br>> > <a href="mailto:Ocfs2-devel@oss.oracle.com">Ocfs2-devel@oss.oracle.com</a> <mailto:<a href="mailto:Ocfs2-devel@oss.oracle.com">Ocfs2-devel@oss.oracle.com</a>>
<br>> > <a href="http://oss.oracle.com/mailman/listinfo/ocfs2-devel">http://oss.oracle.com/mailman/listinfo/ocfs2-devel</a><br>> <<a href="http://oss.oracle.com/mailman/listinfo/ocfs2-devel">http://oss.oracle.com/mailman/listinfo/ocfs2-devel
</a>><br>> ><br>><br>><br>><br>> ------------------------------<br>><br>> _______________________________________________<br>> Ocfs2-devel mailing list<br>> <a href="mailto:Ocfs2-devel@oss.oracle.com">
Ocfs2-devel@oss.oracle.com</a> <mailto:<a href="mailto:Ocfs2-devel@oss.oracle.com">Ocfs2-devel@oss.oracle.com</a>><br>> <a href="http://oss.oracle.com/mailman/listinfo/ocfs2-devel">http://oss.oracle.com/mailman/listinfo/ocfs2-devel
</a><br>><br>><br>> End of Ocfs2-devel Digest, Vol 25, Issue 10<br>> *******************************************<br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> Ocfs2-devel mailing list<br>> <a href="mailto:Ocfs2-devel@oss.oracle.com">Ocfs2-devel@oss.oracle.com</a><br>> <a href="http://oss.oracle.com/mailman/listinfo/ocfs2-devel">
http://oss.oracle.com/mailman/listinfo/ocfs2-devel</a><br>><br></blockquote></div><br>