Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Sep 2006 18:08:15 -0700
From:      George Hartzell <hartzell@alerce.com>
To:        Jonathan Stewart <jonathan@kc8onw.net>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Anyone??? (was Reproducible data corruption on 6.1-Stable)
Message-ID:  <17671.23039.815831.701428@satchel.alerce.com>
In-Reply-To: <450752F6.4050109@kc8onw.net>
References:  <450752F6.4050109@kc8onw.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Stewart writes:
 > [...]
 > I set up a new server recently and transferred all the information from
 > my old server over.  I tried to use unison to synchronize the backup of
 > pictures I have taken and noticed that a large number of pictures where
 > marked as changed on the server.  After checking the pictures by hand I
 > confirmed that many of the pictures on the server were corrupted.  I
 > attempted to use unison to update the files on the server with the
 > correct local copies but it would fail on almost all the files with the
 > message "destination updated during synchronization."
 > 
 > It appears the corruption happens during the read process because when I
 > recompare the files in a graphical diff tool between cache flushes the
 > differences move around!?!?!?  The differences also appear to be very
 > small for the most part, single bytes scattered throughout the file.  I
 > really have no idea what is causing the problem and would like to pin it
 > down so I can either replace hardware if it's bad or fix whatever the
 > bug is.
 > [...]

It might be a memory problem.  I had a linux server that was serving a
subversion repository, plus some web stuff.  I added some additional
memory to keep it from wheezing and it seemed to be running fine.  We
started noticing problems with things that had been checked out of the
repository (e.g. binary tarballs).  Removing the extra memory made
things work again.

memtest86 didn't find anything wrong, which I gather isn't that
unusual in these situations.

Then again, your problem might be something else entirely....


g.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17671.23039.815831.701428>