On Fri, Feb 11, 2011 at 11:15 AM, Guido Günther <a...@sigxcpu.org> wrote:
> On Sat, Feb 12, 2011 at 09:23:09AM +1930, Olaf Reitmaier Veracierta wrote:
> > Hi,
> >
> > It is not the solution because I have two servers using the same GFS2
> > partition.
> >
> > I've done what you said (lock_nolock) but, in that case, I prefer to use
> > EXT3 filesystem to store my files.
> >
> > Still having replicable corruption problems with large file (>6GB) on
> GFS2
> > filesystems.
>
> This was meant as a test! Are you seeing corruption with lock_nolock on
> gfs2?
> -- Guido
>
With lock_nolock option the corruption disappears.
But as I've said, I need locking active because I'm sharing the GFS2
partitions among several servers.
Finally, I uncluster the GFS2 partitions and now I'm using EXT3 again in
manual active/pasive mode in the affected servers.
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.
--
"You don't know where your shadow will fall",
Somebody.-
----------------------------------------------------------------
Olaf Reitmaier Veracierta <ola...@gmail.com>
----------------------------------------------------------------
http://www.olafrv.com
----------------------------------------------------------------
