Serius?? I make many test in 32 bits environment and don't has any problem.....<br><br>I will take another approach and I will put a switch in the interconnect.. (now I has a crossover cable)..<br><br>If still have problems I will look a view of of migrating to 64bits.. :-)<br>
<br>Thanks for the tip :)<br><br><br><div class="gmail_quote">On Fri, Feb 10, 2012 at 1:54 PM, Adi Kriegisch <span dir="ltr"><<a href="mailto:adi@cg.tuwien.ac.at">adi@cg.tuwien.ac.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear Eduardo,<br>
<div class="im"><br>
> I shutdown the filesystem an make a fsck.ocfs2 and there is many<br>
> errors y cluster file but there is no way to test that the ocfs2 are<br>
> ok? I can stop in night but for me this are crazy, because every to<br>
> months the filesystem are broken and if I stop one node the running<br>
> node go down...<br>
><br>
> I have all system in debian squezee with ocfs2 1.6.3<br>
><br>
> Any Ideas??<br>
</div>We had similar issues (also running debian squeeze 32bit). At the time we<br>
suspected having not enough LOWMEM available for the recovery to complete<br>
successfully.<br>
Switching to amd64 solved the issue for us. Luckily ocfs2 is able to run<br>
with mixed 32bit and 64bit clients so we could migrate our servers one by<br>
one without too much interrupting production.<br>
<span class="HOEnZb"><font color="#888888"><br>
-- Adi<br>
</font></span></blockquote></div><br>