On 3 Mar 2010, at 5:57am, Collin Capano wrote: > I've been running into some disk I/O errors when doing things such as > vacuuming and/or inserting things into temp tables in a database. The > databases that are giving me trouble are quite large: between 29 and > 55GB. However, as large as that is, I don't think running out of disk > space is the issue as I have about 3TB of free space on the disk. So, my > question is, is there a maximum size that databases can be?
Nothing of that level built into SQLite. And even if there was, it would not produce an i/o error, it would complain about pages or filesize. Run a hardware check on your computer: one of those programs which reads every sector of the disk and checks other pieces of hardware. The other thing to do would be to use the command-line tools to turn your database into SQL commands, then use those commands to create a new database file, then delete the old database file and rename the new one. This would definitively get rid of any structure problems in your database file and make sure it wasn't occupying any faulty disk sectors. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
