[Digikam-devel] problems with digikam3.db into a nefs partition

[Gilles Caulier]

ok

In all case i think than using a NFS mount point like a root album library
path is wrong, because there is a risk to have 2 instance of digiKAm running
on 2 different computers witch open the database in R/W. In this case, the
concurrent writting on DB will corrupt the data.

The database file must be stored in all case in local. The way to have a
link on NFS mount path like a subfolder of the root album library path is an
easy solution. each computer have a dedicaced database file in local. No
problem with NFS, no concurrent acess to DB.

Gilles

2007/3/7, Fabien <fabien.ubuntu at gmail.com>:
>
> Gilles Caulier wrote:
> >
> >
> > 2007/3/7, Fabien <fabien.ubuntu at gmail.com
> > <mailto:fabien.ubuntu at gmail.com>>:
> >
> >     Hi,
> >
> >     Gilles Caulier wrote:
> >      > Try to stress the database using a large taging image/comment or
> >     rating.
> >      > The problem apprears about multiple access on DB duing a wrong DB
> >     lock.
> >
> >     I tried, but without success :) I even tried to update comments/tags
> >     while copying images, did the same with 2 instances of digiKam.
> >     I managed to make digiKam crash once, but didn't have troubles with
> >     sqlite !
> >
> >
> > Perhaps the SQLite/NFS problem ios relevant of NFS deamon settings or
> > about to set on the NFSLock deamon at the same time than NFSd ?
>
> Well, I use my own compiled linux kernel with kernel-based nfs server
> (same for lockd)...
> I don't have any specific settings.
> But I read in sqlite mailing list archives that some people have
> troubles when mixing freebsd server and linux clients...
>
> --
> Fabien
>
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-devel/attachments/20070307/98d9fc13/attachment.html>