Re: [sqlite] corruption problem with attached macintosh database
> >Have you tried with this turned on: > > http://www.sqlite.org/compile.html#enable_locking_style Enabling this causes link errors under my version of OSX, due to the absence of "gethistuuid". I see some traffic on the web that suggests this comes in a later OSX. (I use 10.4.11) Also, this seems to be an API-free option that "does the right thing", but there is no apparent way to tell what option it is selecting, or for that matter, what locking is used under any circumstances. It would be useful to have a specific piece of information, "locking using strategy x" which I could derive and perhaps verify dissonant locking strategies as the source of the problem now, and if it ought to be fixed by enabling the fancier locking code. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] corruption problem with attached macintosh database
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Dyer wrote: > whatever is default. I compile mu own sqlite static libraries, but > I don't customize the settings. Have you tried with this turned on: http://www.sqlite.org/compile.html#enable_locking_style Roger -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkusvgAACgkQmOOfHg372QT+NACgusVJHibAoiCN4P3G5Z8M/vlu 5HEAn3O1pTTpezV5M/cA2UmWi84U/fHO =EPXO -END PGP SIGNATURE- ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] corruption problem with attached macintosh database
> > >What journaling mode are you using? whatever is default. I compile mu own sqlite static libraries, but I don't customize the settings. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] corruption problem with attached macintosh database
On Wed, Mar 24, 2010 at 7:20 PM, Dave Dyerwrote: > > > > >Could you help us by adding any of the following details ? > > > >What OS is the Mac running ? > > OSX 10.4.11 for me, but also snow leopard. > > >What OS is the PC running ? > > Windows 2003 server for me, but also XP (note the file systems are all mac > file systems) > > >What protocol is being used to access the Mac file share ? > > Presumably windows standard file sharing protocol over tcp > > >Is the file-sharing host accessing the database as a shared file, or as a > file on its hard disk ? > > The mac acting as file host is accessing the file as a local file. > > > >Does this happen without any data-changing instructions ? In other words > can I get this fault using only _open, ATTACH and lots of SELECT commands > until something falls over ? Or even just repeated _open, ATTACH and _close > until something falls over ? > > No data on this question. The purpose of this querty setup > is to copy some data into an auxialiary database. > > >> Note that the main database, which is updated periodically, doesn't have > >> a corruption problem, > > > >Are both 'main' and 'auxiliary' on in the same folder, being accessed the > same way ? > > Yes. And significantly, there is no corruption problem with simultaneous > updates to the main database. > > > >> and that this is only a problem with databases resident > >> on a mac. The same scenario, with databases resident on the PC disk, > works > >> fine. > > > >When the databases are on the PC disk, what protocol is the Mac using to > access them ? > > Presumably the same. Before recent versions of OSX this kind of access > used "samba" server. > > > What journaling mode are you using? ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] corruption problem with attached macintosh database
> >Could you help us by adding any of the following details ? > >What OS is the Mac running ? OSX 10.4.11 for me, but also snow leopard. >What OS is the PC running ? Windows 2003 server for me, but also XP (note the file systems are all mac file systems) >What protocol is being used to access the Mac file share ? Presumably windows standard file sharing protocol over tcp >Is the file-sharing host accessing the database as a shared file, or as a file >on its hard disk ? The mac acting as file host is accessing the file as a local file. >Does this happen without any data-changing instructions ? In other words can >I get this fault using only _open, ATTACH and lots of SELECT commands until >something falls over ? Or even just repeated _open, ATTACH and _close until >something falls over ? No data on this question. The purpose of this querty setup is to copy some data into an auxialiary database. >> Note that the main database, which is updated periodically, doesn't have >> a corruption problem, > >Are both 'main' and 'auxiliary' on in the same folder, being accessed the same >way ? Yes. And significantly, there is no corruption problem with simultaneous updates to the main database. >> and that this is only a problem with databases resident >> on a mac. The same scenario, with databases resident on the PC disk, works >> fine. > >When the databases are on the PC disk, what protocol is the Mac using to >access them ? Presumably the same. Before recent versions of OSX this kind of access used "samba" server. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] corruption problem with attached macintosh database
On 24 Mar 2010, at 8:50pm, Dave Dyer wrote: > database resident on a mac file sustem > mounted as a drive letter on a pc > the "main" database is open and shared by sqlite running on both computers. > the "auxiliary" database is attached and updated simultaneously from both > computers> Could you help us by adding any of the following details ? What OS is the Mac running ? What OS is the PC running ? What protocol is being used to access the Mac file share ? Is the file-sharing host accessing the database as a shared file, or as a file on its hard disk ? > Under these circumstances, both applications typically get > "error 11, disk image is corrupted" errors while attempting > to update the auxiliary database. Does this happen without any data-changing instructions ? In other words can I get this fault using only _open, ATTACH and lots of SELECT commands until something falls over ? Or even just repeated _open, ATTACH and _close until something falls over ? > Note that the main database, which is updated periodically, doesn't have > a corruption problem, Are both 'main' and 'auxiliary' on in the same folder, being accessed the same way ? > and that this is only a problem with databases resident > on a mac. The same scenario, with databases resident on the PC disk, works > fine. When the databases are on the PC disk, what protocol is the Mac using to access them ? Thanks for your help. Simon. ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users