Re: [Koha-devel] mysqldump & restore issues

Joe, Thanks for the information. I think I'll just try restoring the mysqldump on a a physical host and see if I have the same problems. If it works, I'll build another VM with fixed-size storage and hopefully that will be the end of my worries. I'm hoping to not have to look too closely a

Re: [Koha-devel] mysqldump & restore issues

For those who didn't read the pasted logs, one link they mentioned is here: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listi

Re: [Koha-devel] mysqldump & restore issues

I wouldn't be surprised if this was related to dynamic allocation on the VM. Essentially, it can inject a random very large I/O latency to any operation. It may also change the hardware model used by the VM. I would recommend looking at InnoDB diagnostics, and possibly starting up w/ innodb_forc

Re: [Koha-devel] mysqldump & restore issues

Thanks, Mike. I'll try your recommendations and post back what I find out. Cheers, Christopher Curry Assistant Technical Librarian / Assistant IT Officer American Philosophical Society 105 South Fifth Street Philadelphia, PA 19106-3386 Tel. (215) 599-4299 ccu...@amphilsoc.org

Re: [Koha-devel] mysqldump & restore issues

It could still be memory, because MySQL keeps indexes and such in memory. It could also be a bad sector on the disk, because MySQL caches query results to disk when they are bigger than the space allocated in memory for query results. The only character I can think of that would cause trouble in t

Re: [Koha-devel] mysqldump & restore issues

Mike, Thanks for the reply. I did try querying individual records around that row; in fact, I used "limit 41536,1" to find out the specific biblioitemnumber. I checked the record in Koha and found no problems with it or adjacent records and I had no problem querying these individual records