I failed over the server and ran a short backup and there were no
"didn't compare" errors where on the first server, they are there
pretty reliably. I guess this confirms some hardware on the first
server is flipping bits. Essentially, users could have any number of
munged files (most files are binary) since the problem surfaced a few
weeks ago, and there'd be know way to know. Unfortunately, the
secondary server was off for a short time at one point, so even if
the munging were taken place on the I/O subsystem and not in RAM, it
is possible that some blocks got copied badly to the secondary server.
Anyway, it seems the problem is definitely hardware and not due to
either ext3, drbd or mysql!
--
Maurice Volaski, [EMAIL PROTECTED]
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
