<br><br><div class="gmail_quote">On Fri, Feb 11, 2011 at 11:15 AM, Guido Günther <span dir="ltr"><<a href="mailto:agx@sigxcpu.org">agx@sigxcpu.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sat, Feb 12, 2011 at 09:23:09AM +1930, Olaf Reitmaier Veracierta wrote:<br>
> Hi,<br>
><br>
> It is not the solution because I have two servers using the same GFS2<br>
> partition.<br>
><br>
> I've done what you said (lock_nolock) but, in that case, I prefer to use<br>
> EXT3 filesystem to store my files.<br>
><br>
> Still having replicable corruption problems with large file (>6GB) on GFS2<br>
> filesystems.<br>
<br>
</div>This was meant as a test! Are you seeing corruption with lock_nolock on<br>
gfs2?<br>
<font color="#888888"> -- Guido<br>
</font></blockquote></div><br>With lock_nolock option the corruption disappears.<br><br>But as I've said, I need locking active because I'm sharing the GFS2 partitions among several servers.<br><br>Finally, I uncluster the GFS2 partitions and now I'm using EXT3 again in manual active/pasive mode in the affected servers.<br>
<br>But I really want to get this bug away because when my other servers reach files over 6GB the bug will appears in these servers too.<br><br>-- <br> "You don't know where your shadow will fall",<br> Somebody.-<br>
----------------------------------------------------------------<br> Olaf Reitmaier Veracierta <<a href="mailto:olafrv@gmail.com">olafrv@gmail.com</a>><br>----------------------------------------------------------------<br>
<a href="http://www.olafrv.com">http://www.olafrv.com</a><br>----------------------------------------------------------------<br>