very slow on mounts

[Michael Stoehrel]

Hi

I just realized that digikam is very slow on a net mount, or dying.
Normally I store all my data on a server (hd is mirrored, backuped,...)
But after copying all album back to the server and restarting digikam
(changed the path in digikamrc) it tooks hours and nothing happend.

I mount a smb share with cifs static in fstab.

Michael
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Arnd Baecker]

Hi Michael,

On Sat, 12 Apr 2008, Michael Stoehrel wrote:

> Hi
>
> I just realized that digikam is very slow on a net mount, or dying.
> Normally I store all my data on a server (hd is mirrored, backuped,...)
> But after copying all album back to the server and restarting digikam
> (changed the path in digikamrc) it tooks hours and nothing happend.
>
> I mount a smb share with cifs static in fstab.

Ok, that's most likely the source of the problem:
the database file (digikam3.db) is on a NFS/smb share.
This is not supported due to limitations of the underlying sqlite
database.

For background/workarounds see this FAQ entry:
  http://www.digikam.org/?q=node/219

With digikam 0.10 multiple root albums will be possible,
including that the database is on a different disk than
the images themselves.

Best, Arnd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Andreas Weigl]

Hi

Am Sunday 13 April 2008 schrieb Arnd Baecker:
> > I just realized that digikam is very slow on a net mount, or dying.
> > Normally I store all my data on a server (hd is mirrored, backuped,...)
> > But after copying all album back to the server and restarting digikam
> > (changed the path in digikamrc) it tooks hours and nothing happend.
> >
> > I mount a smb share with cifs static in fstab.

NFS has the option nolock. I do not know if smb knows it too.
I know that other Unix Systems "included" smb in NFS so basically some of the
options for nfs work with smb too.

> Ok, that's most likely the source of the problem:
> the database file (digikam3.db) is on a NFS/smb share.
> This is not supported due to limitations of the underlying sqlite
> database.

As I already stated in the thread "Albumroot on remote filesystem", the basic
problem is that locking doesn't work properly on network filesystems.
With nolock the locks are set on the local machine only and everything works
fine.

Andreas
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users