Dennis Kellly
11/08/2011 11:11 AM
post89941
|
>>>qdb: processing [mme_temp]/db/mme_temp.sql - disk I/O error
I am guessing this file is located in shared memory? If so, I suspect the failure is due to the filesystem not
supporting full posix semantics.
As a quick test, try
# devb-ram ram capacity=8192
# dinit –h /dev/hd1t77 <<<< careful that /dev/hd1 is ramdisk!!!
# mount /dev/hd1t77 /tmp2
Now change the location of the file to reside under /tmp2 and see if it works.
|
|
|
Ryan Allen(deleted)
11/08/2011 11:57 AM
post89944
|
/Fs/tmpfs/ provided by io-fs -dtmp should be fine as a filesystem to store
the databases.
Are there any other files in /fs/tmpfs/ ? Perhaps a lock file or
something similar that sqlite is honoring but that your attempt to write
to the file ignores.
Have you made any modifications to the .sql files? Initially I would be
trying this with the default files. Can you read all of the .sql files
without error (try simply to "cat" the files from the shell).
To try to narrow down the error I would first try to clear all files in
/fs/tmpfs/ (simple to do: just kill io-fs-media and re-start it), then
start with a simplified config file. Try specifying only one database
(for example, just mme_temp and not mme or mme_library) to see if qdb will
start. If this still fails you could see if adding some tracing to sqlite
will help; if a query is causing a problem then this will show the
specific query. You do this by adding arguments:
qdb -otempstore=/fs/tmpfs/,trace,profile -vvvvvv
(At least six -v's.)
Generally speaking the default configuration should "just work", as long
as all of the files are in the right places.
--
Ryan J. Allen
QNX Software Systems
|
|
|