I hope not :)
It's under continuous load the whole day already (we write log files on it that are several GB per file per day) Isn't it strange that no other query that I execute from sqlite shell has this , just the one error the correlated sub query? Anyhow, I'll ask our sysadmins for a disk assessment tool. Thanks for your help! Gunnar . On 2015-05-27 17:55, Simon Slavin wrote: > On 27 May 2015, at 4:42pm, gunnar <gharms at hiqinvest.nl> wrote: > >> And it got 'stuck' after displaying a couple hundred records or so. And the >> stack trace is then: #0 0x00000034f020ec50 in __lseek_nocancel () from >> /lib64/libpthread.so.0 #1 0x000000000041a42c in seekAndRead () #2 >> 0x000000000041a5f9 in unixRead () #3 0x0000000000410a86 in sqlite3OsRead () > > That is at the hardware level or extremely close to it. Is it possible that > your error is caused by hardware rather than software ? Can you run some disk > assessment tools on that hard disk ? Or put it under continuous load for a > while using something that doesn't involve SQLite ? > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users [1] Links: ------ [1] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
