On Sat, Jan 14, 2017 at 5:04 PM, Simon Slavin <slav...@bigfraud.org> wrote:
> > On 15 Jan 2017, at 1:01am, Kevin O'Gorman <kevinogorm...@gmail.com> wrote: > > > Update: the integrity check said "ok" after about 1/2 hour. > > the record count now takes about 4 seconds -- maybe I remembered wrong > and > > it always took this long, but I wasn't stopping it until it had hung for > > several minutes. > > What you describe actually sounds more like a hardware problem. You had a > 'sticky' disk, affecting at least some of the sectors in which that > database is stored, which has now sorted itself out. But sometime in the > future it may become sticky again. If you have some sort of disk checking > software you might like to try it. > > Given your 5 indexes, 30 minutes to check an 11GB file is completely > reasonable. Don’t worry about that. > > Good luck with it. > It turns out you're right about the time for a check. However, I don't buy the "sticky disk" idea. I could copy the files just fine. I could create a new file of the same size just fine. But sqlite3 was stuck. How does that happen? I don't know, and my imagination is stuck. -- word of the year: *kakistocracy* _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
