<html><body bgcolor="#FFFFFF"><div><span class="Apple-style-span" style="-webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); ">On 2010-12-16, at 6:47, Jeremy Filizetti <<a href="mailto:jeremy.filizetti@gmail.com">jeremy.filizetti@gmail.com</a>> wrote:</span></div><blockquote type="cite"><div><div class="gmail_quote">On Wed, Nov 10, 2010 at 5:40 AM, Andreas Dilger <span dir="ltr"><<a href="mailto:andreas.dilger@oracle.com"><a href="mailto:andreas.dilger@oracle.com">andreas.dilger@oracle.com</a></a>></span> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">In fact, this config llog copying should only be done on the first mount of the OST, or if the configuration has changed.<br>
<br>
We've actually removed this entirely for the 2.4 release, though that doesn't help you now.<br></blockquote><div><br>Does that mean the llog component of Lustre is completely removed? Is 2.4 an Oracle only release?</div></div>
</div></blockquote><br><div>No, only that the copying of the config llog from the MGS to the OST has been removed. The llog subsystem still is used to maintain distributed operation consistency.</div><div><br></div><div>"Lustre 2.4" is the anticipated release number when that change might become available. As yet, it is still pre-alpha code, and while this change is available in bugzilla as a series of patches, it would need some effort to port it for 1.8.</div><div><br></div><div>Cheers, Andreas</div></body></html>