Thoughts on Rails

Riding the Train of Thought

Digikam Albums on Network Filesystem

with 4 comments

Digikam has issues with albums on a network share. It uses sqlite database, and it seems that the database file cannot be stored on a share.

Click here for the bug report…

Now, I was stumped when Digikam refused to work the first time, I thought it was because of the overwhelming number of photographs that I threw at it – 30GB, over network. So I reduced it to 12MB… nothing happened. That’s when I sensed that something is wrong.

The above bug report almost washed away all hopes of having my files on a central fileserver and accessing them from the various machines around me. I went to sleep at 6 am, thinking about this… woke up for lunch, and woke up with an idea – I mounted the share on a directory which is outside the path of Digikam’s library, then I symlinked the directory into the library. So now basically, the sqlite database sits on my local harddisk, but the files are accessed from the server – problem solved!

Library: /home/harshad/images/

Share mounted on: /home/harshad/shared/

Actual photos on: /home/harshad/shared/photos/2007/


ln -s /home/harshad/shared/photos/2007 /home/harshad/images/shared

I should mention that it works fine when I have the sample images amounting upto 12MB… when I gave it the whole library, it loaded the information into the database, but after showing no further progress for more than 30 minutes, I terminated it.

I think I’ll have to have various symlinks for smaller sections of my library and have shell scripts to create / delete these symlinks before loading digikam to make it lighter on the software and network!

Hope this issue is solved and we don’t need this workaround.

Note: Edited on 5 March 2007 for some typos.

Written by hiway

March 3, 2007 at 3:32 am

4 Responses

Subscribe to comments with RSS.

  1. It looks like we came up with similar workarounds to the digiKam network issue (

    I don’t have nearly as many photos as you do, so I haven’t run into the other issue that you mentioned, yet.


    April 1, 2007 at 2:30 am

  2. Thank you Micron. Also read up on your solution… and thanks for linking back here.

    My main issue has been the number of photos that I am trying to handle. So far only Picasa (on windows) has been able to work smoothly with 512 MB of RAM. Lightroom needs almost a gigabyte, BlueMarine can adjust, but I’m still trying to get a grip on how it works… DigiKam is by far the best for UNIX world, but the menus and popup windows for editing creep me out.

    However, one cant stop loving fantastic software like DigiKam 🙂


    April 1, 2007 at 12:10 pm

  3. I moved my folder to a vfat partition. It was bad luck that I didn’t have any other place free to store all of these pictures.

    The problem that arose was that the lower/upper case writing got somehow mangled, and furthermore these entries would exists twice in the Digikam database.

    These where the commands I just to fix all of that:
    # ‘move folders’, so update information
    UPDATE Albums SET url = ‘/serverFotos’ || url;
    # delete all upper case pictures where the same lower case version would exist
    DELETE FROM Images WHERE LOWER(name) != name AND LOWER(name) IN (SELECT name FROM Images);

    It’s running smoothly now. Thanks for the hint


    January 7, 2008 at 3:53 pm

  4. Hi Chris, thanks for the valuable info! I’m sure it will be useful to anybody who has a messed up sqlite database for digikam with case or album relocated or moved.


    P.S. Also tried to add search keywords within my reply for people who might be looking for it. 😉


    January 7, 2008 at 4:09 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: