mySQL error

[calvorn]

Hi:

I have been running RC4 for a while now without a problem. I just did a back-up of the Db and now get this on all pages:

Warning: mysql_data_seek(): Offset 0 is invalid for MySQL result index 6 (or the query data is unbuffered) in /home/calvorn/www/www/gallery/language.php on line 108

Warning: mysql_data_seek(): Offset 0 is invalid for MySQL result index 6 (or the query data is unbuffered) in /home/calvorn/www/www/gallery/language.php on line 129

Warning: mysql_data_seek(): Offset 0 is invalid for MySQL result index 6 (or the query data is unbuffered) in /home/calvorn/www/www/gallery/language.php on line 145

Warning: mysql_data_seek(): Offset 0 is invalid for MySQL result index 6 (or the query data is unbuffered) in /home/calvorn/www/www/gallery/language.php on line 250

Notice: Undefined variable: s_lazy_language in /home/calvorn/www/www/gallery/fetchsettings.php on line 273

Anybody have any idea what happened? I swear I didn't change anything so don't know what happened. I did a restore and stilll get the same results. I thought language.php might have gotten corrupt so I reuploaded that but it didn't fix anything.

Thanks.

Cal

[calvorn]

Found the problem--tables corrupted.

How did it happen? Not sure but my ISP has a strict limit on server space. In fact, it seems you get your own parition but when it's full that's it--you have to move everything to a new server with bigger partitions.

I had very little space left and whenever I backed-up these last few weeks my back-up was getting truncated.

I did not see any indication of this and assumed the back-up was ok. It restored ok and the CRC checks were fine but some of the tables were corrupt.

I did a db dump last week using phpMyAdmin and that restored fine. I would recommend this--pretty simple with phpMyAdmin.

[Pekka]

If you do file backups with EE Backup it will tell you on report tab if the file was saved successfully, and also you can see in the end of it a summary and backup status info. If you run out of disk space or the backup is not complete you will know.

The database backups are bit different, because they are stored in the database - many servers have a size quota for SQL and AFAIK there is no way knowing how much space you have left. When SQL server space is low it is up to MySQL to handle that situation and report it and you should always get an MySQL error message. The EE Backup's CRC info is really accurate info if the backup block was saved properly or not because after the data is saved it is read back that CRC's is compared with one in the memory. These things make me wonder if the problem was in MySQL at all and the backup sets were fine. Perhaps the restore ran out of PHP RAM or had timeout. If you still have one of those bad sets, can you save that set data to file and see how it looks in text editor.