file not found.... -> no start!

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

file not found.... -> no start!

Uwe Haider
After moving to a new computer/NAS I have trouble to start digikam. I
try to fix it for several weeks now, but no success so far. This is the
output of digikam while starting:

  [...]

  133  digikam.general: Using  8  CPU core to run threads
  134 digikam.general: new search text settings:  "" : hasResult =
false , validRows =  0
  135 QFSFileEngine::open: No file name specified
  136 digikam.geoiface: ----
  137 digikam.general: Added root album called:  "WD-USB"
  138 digikam.general: Added root album called:  "Geschäftsbericht_2011"
  139 digikam.general: Added root album called:  "Einweihung HHN"
  140 digikam.general: Added root album called:  "Albas Bilder"
  141 digikam.general: Added root album called:  "Carla 18"
  142 digikam.general: Added root album called:  "Bilder_lokal"
  143 digikam.general: Added root album called:  "Bilder"
  144 digikam.general: Added root album called:  "Fotos"
  145 digikam.general: Added root album called:  "NAS"
  146 digikam.general: Did not find album root album in hash
  147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden
  148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden

-> last line is repeated until here

3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden
3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar

"Datei oder Verzeichnis nicht gefunden" means "file not found"

"Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
left on device".

This is, what I have done while moving to the new machine:

- moved the mariadb-server to my NAS

- moved all files in the NAS-mariadb as separate dumps

- changed the album paths in the albumroot-table to the new mount points

- I have lost an harddisk (broken, unreadable) and tried to mount the
backup instead ( I don't need this files absolut)

- changed the configuration in digikam to the NAS-mariadb

The main problem seems to be the QInotifyFileSystemWatcherEngine writing
a disk full - how can I stop this? I think digikam will be able to check
and repare the mariadb if it gets started.

Or should I remove the Albumrootpath of the crashed hard disk manually?


Any advice is welcome...


uhai



--
Uwe Haider
[hidden email]
http://www.familie-haider.de


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: file not found.... -> no start!

AndriusWild
I would make sure you have write access to the NAS.  On some systems, e.g. Fedora it is a bit complicated to mount an NTFS drive with full access (read and write).
You can try:
"nano /path/to/nas/temp.txt"
then add some text in temp.txt and save it.
Instead of "nano" you can use "gedit" if you are on gnome or "kate" if you are on KDE.
Please run it from your user account and do not use "sudo".
Just an idea.


Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Uwe Haider <[hidden email]>
Date: 2017-05-21 6:23 AM (GMT-07:00)
Subject: file not found.... -> no start!

After moving to a new computer/NAS I have trouble to start digikam. I
try to fix it for several weeks now, but no success so far. This is the
output of digikam while starting:

  [...]

  133  digikam.general: Using  8  CPU core to run threads
  134 digikam.general: new search text settings:  "" : hasResult =
false , validRows =  0
  135 QFSFileEngine::open: No file name specified
  136 digikam.geoiface: ----
  137 digikam.general: Added root album called:  "WD-USB"
  138 digikam.general: Added root album called:  "Geschäftsbericht_2011"
  139 digikam.general: Added root album called:  "Einweihung HHN"
  140 digikam.general: Added root album called:  "Albas Bilder"
  141 digikam.general: Added root album called:  "Carla 18"
  142 digikam.general: Added root album called:  "Bilder_lokal"
  143 digikam.general: Added root album called:  "Bilder"
  144 digikam.general: Added root album called:  "Fotos"
  145 digikam.general: Added root album called:  "NAS"
  146 digikam.general: Did not find album root album in hash
  147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden
  148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden

-> last line is repeated until here

3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden
3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar

"Datei oder Verzeichnis nicht gefunden" means "file not found"

"Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
left on device".

This is, what I have done while moving to the new machine:

- moved the mariadb-server to my NAS

- moved all files in the NAS-mariadb as separate dumps

- changed the album paths in the albumroot-table to the new mount points

- I have lost an harddisk (broken, unreadable) and tried to mount the
backup instead ( I don't need this files absolut)

- changed the configuration in digikam to the NAS-mariadb

The main problem seems to be the QInotifyFileSystemWatcherEngine writing
a disk full - how can I stop this? I think digikam will be able to check
and repare the mariadb if it gets started.

Or should I remove the Albumrootpath of the crashed hard disk manually?


Any advice is welcome...


uhai



--
Uwe Haider
[hidden email]
http://www.familie-haider.de


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: file not found.... -> no start!

Remco Viëtor
In reply to this post by Uwe Haider
On dimanche 21 mai 2017 14:23:29 CEST Uwe Haider wrote:

> After moving to a new computer/NAS I have trouble to start digikam. I
> try to fix it for several weeks now, but no success so far. This is the
> output of digikam while starting:
>
>   [...]
>
>   133  digikam.general: Using  8  CPU core to run threads
>   134 digikam.general: new search text settings:  "" : hasResult =
> false , validRows =  0
>   135 QFSFileEngine::open: No file name specified
>   136 digikam.geoiface: ----
>   137 digikam.general: Added root album called:  "WD-USB"
>   138 digikam.general: Added root album called:  "Geschäftsbericht_2011"
>   139 digikam.general: Added root album called:  "Einweihung HHN"
>   140 digikam.general: Added root album called:  "Albas Bilder"
>   141 digikam.general: Added root album called:  "Carla 18"
>   142 digikam.general: Added root album called:  "Bilder_lokal"
>   143 digikam.general: Added root album called:  "Bilder"
>   144 digikam.general: Added root album called:  "Fotos"
>   145 digikam.general: Added root album called:  "NAS"
>   146 digikam.general: Did not find album root album in hash
>   147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
> failed: Datei oder Verzeichnis nicht gefunden
>   148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
> failed: Datei oder Verzeichnis nicht gefunden
>
> -> last line is repeated until here
>
> 3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
> failed: Datei oder Verzeichnis nicht gefunden
> 3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
> failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
>
> "Datei oder Verzeichnis nicht gefunden" means "file not found"
>
> "Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
> left on device".
>
> This is, what I have done while moving to the new machine:
>
> - moved the mariadb-server to my NAS
>
> - moved all files in the NAS-mariadb as separate dumps
>
> - changed the album paths in the albumroot-table to the new mount points
>
> - I have lost an harddisk (broken, unreadable) and tried to mount the
> backup instead ( I don't need this files absolut)
>
> - changed the configuration in digikam to the NAS-mariadb
>
> The main problem seems to be the QInotifyFileSystemWatcherEngine writing
> a disk full - how can I stop this? I think digikam will be able to check
> and repare the mariadb if it gets started.
>
> Or should I remove the Albumrootpath of the crashed hard disk manually?
>
>
> Any advice is welcome...
>
>
> uhai
If I understand correctly, you are trying to put the digikam database on a
network drive. Looking at the Digikam settings dialog, it says explicitly:
"Note: a remote file system such as NFS, cannot be used here"...
In addition, MySQL is still marked as experimental, mariadb is a fork of
MySQL. That's for Digikam version 5.5.0 (as appimage under OpenSuSE 42.2)

Might that be the cause of the problems?

Remco
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: file not found.... -> no start!

Gilles Caulier-4
I confirm,

Never place a sqlite database on a network device. sqlite, even if
implementation is better in time, will don't support well the lock
mechanism on network place. Read the entry in this wiki for details :

http://stackoverflow.com/questions/788517/sqlite-over-a-network-share

Gilles Caulier

2017-05-21 15:50 GMT+02:00 Remco Viëtor <[hidden email]>:

> On dimanche 21 mai 2017 14:23:29 CEST Uwe Haider wrote:
>> After moving to a new computer/NAS I have trouble to start digikam. I
>> try to fix it for several weeks now, but no success so far. This is the
>> output of digikam while starting:
>>
>>   [...]
>>
>>   133  digikam.general: Using  8  CPU core to run threads
>>   134 digikam.general: new search text settings:  "" : hasResult =
>> false , validRows =  0
>>   135 QFSFileEngine::open: No file name specified
>>   136 digikam.geoiface: ----
>>   137 digikam.general: Added root album called:  "WD-USB"
>>   138 digikam.general: Added root album called:  "Geschäftsbericht_2011"
>>   139 digikam.general: Added root album called:  "Einweihung HHN"
>>   140 digikam.general: Added root album called:  "Albas Bilder"
>>   141 digikam.general: Added root album called:  "Carla 18"
>>   142 digikam.general: Added root album called:  "Bilder_lokal"
>>   143 digikam.general: Added root album called:  "Bilder"
>>   144 digikam.general: Added root album called:  "Fotos"
>>   145 digikam.general: Added root album called:  "NAS"
>>   146 digikam.general: Did not find album root album in hash
>>   147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Datei oder Verzeichnis nicht gefunden
>>   148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Datei oder Verzeichnis nicht gefunden
>>
>> -> last line is repeated until here
>>
>> 3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Datei oder Verzeichnis nicht gefunden
>> 3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
>> failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
>>
>> "Datei oder Verzeichnis nicht gefunden" means "file not found"
>>
>> "Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
>> left on device".
>>
>> This is, what I have done while moving to the new machine:
>>
>> - moved the mariadb-server to my NAS
>>
>> - moved all files in the NAS-mariadb as separate dumps
>>
>> - changed the album paths in the albumroot-table to the new mount points
>>
>> - I have lost an harddisk (broken, unreadable) and tried to mount the
>> backup instead ( I don't need this files absolut)
>>
>> - changed the configuration in digikam to the NAS-mariadb
>>
>> The main problem seems to be the QInotifyFileSystemWatcherEngine writing
>> a disk full - how can I stop this? I think digikam will be able to check
>> and repare the mariadb if it gets started.
>>
>> Or should I remove the Albumrootpath of the crashed hard disk manually?
>>
>>
>> Any advice is welcome...
>>
>>
>> uhai
> If I understand correctly, you are trying to put the digikam database on a
> network drive. Looking at the Digikam settings dialog, it says explicitly:
> "Note: a remote file system such as NFS, cannot be used here"...
> In addition, MySQL is still marked as experimental, mariadb is a fork of
> MySQL. That's for Digikam version 5.5.0 (as appimage under OpenSuSE 42.2)
>
> Might that be the cause of the problems?
>
> Remco
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Re: file not found.... -> no start!

Uwe Haider
In reply to this post by Uwe Haider
My NAS is connected via nfs. DigikamDB is mysql. If I remember correctly, only Sqlite can't be used over nfs - right or wrong?

Am 22. Mai 2017 14:00:05 MESZ schrieb [hidden email]:
Send Digikam-users mailing list submissions to
[hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/digikam-users
or, via email, send a message with subject or body 'help' to
[hidden email]

You can reach the person managing the list at
[hidden email]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Digikam-users digest..."


Today's Topics:

1. Re: file not found.... -> no start! (Remco Viëtor)
2. Re: Adjusting file last modified date (Andrey Goreev)
3. Re: file not found.... -> no start! (Uwe Haider) (Uwe Haider)
4. Re: file not found.... -> no start! (Gilles Caulier)
5. Re: How do I save "DateTime imported" value in Digikam?
(Jens Benecke)





Message: 1
Date: Sun, 21 May 2017 15:50:00 +0200
From: Remco Viëtor <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
power of open source <[hidden email]>
Subject: Re: file not found.... -> no start!
Message-ID: <5388231.gBvAhygMuy@manticore>
Content-Type: text/plain; charset="UTF-8"

On dimanche 21 mai 2017 14:23:29 CEST Uwe Haider wrote:
After moving to a new computer/NAS I have trouble to start digikam. I
try to fix it for several weeks now, but no success so far. This is the
output of digikam while starting:

[...]

133 digikam.general: Using 8 CPU core to run threads
134 digikam.general: new search text settings: "" : hasResult =
false , validRows = 0
135 QFSFileEngine::open: No file name specified
136 digikam.geoiface: ----
137 digikam.general: Added root album called: "WD-USB"
138 digikam.general: Added root album called: "Geschäftsbericht_2011"
139 digikam.general: Added root album called: "Einweihung HHN"
140 digikam.general: Added root album called: "Albas Bilder"
141 digikam.general: Added root album called: "Carla 18"
142 digikam.general: Added root album called: "Bilder_lokal"
143 digikam.general: Added root album called: "Bilder"
144 digikam.general: Added root album called: "Fotos"
145 digikam.general: Added root album called: "NAS"
146 digikam.general: Did not find album root album in hash
147 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden
148 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden

-> last line is repeated until here

3094 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Datei oder Verzeichnis nicht gefunden
3095 QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch
failed: Auf dem Gerät ist kein Speicherplatz mehr verfügbar

"Datei oder Verzeichnis nicht gefunden" means "file not found"

"Auf dem Gerät ist kein Speicherplatz mehr verfügbar" means "no space
left on device".

This is, what I have done while moving to the new machine:

- moved the mariadb-server to my NAS

- moved all files in the NAS-mariadb as separate dumps

- changed the album paths in the albumroot-table to the new mount points

- I have lost an harddisk (broken, unreadable) and tried to mount the
backup instead ( I don't need this files absolut)

- changed the configuration in digikam to the NAS-mariadb

The main problem seems to be the QInotifyFileSystemWatcherEngine writing
a disk full - how can I stop this? I think digikam will be able to check
and repare the mariadb if it gets started.

Or should I remove the Albumrootpath of the crashed hard disk manually?


Any advice is welcome...


uhai
If I understand correctly, you are trying to put the digikam database on a
network drive. Looking at the Digikam settings dialog, it says explicitly:
"Note: a remote file system such as NFS, cannot be used here"...
In addition, MySQL is still marked as experimental, mariadb is a fork of
MySQL. That's for Digikam version 5.5.0 (as appimage under OpenSuSE 42.2)

Might that be the cause of the problems?

Remco





Message: 2
Date: Sun, 21 May 2017 08:18:20 -0600
From: Andrey Goreev <[hidden email]>
To: digiKam - Home Manage your photographs as a professional with the
power of open source <[hidden email]>
Subject: Re: Adjusting file last modified date
Message-ID: <[hidden email]>
Content-Type: text/plain; charset="utf-8"

I am pretty sure that FileModifyDate is the system's "date modified". Windows would have "date created" in addition to it but linux does not store "date created". In the example I sent I copy values from QuickTime Date Created of mp4 file to system's file date modified (I do that because digikam uses date modified (file system) as date created (content) for video files. Works for me)


Sent from my Samsung Galaxy smartphone.
-------- Original message --------From: Remco Viëtor <[hidden email]> Date: 2017-05-21 7:43 AM (GMT-07:00) To: digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]> Subject: Re: Adjusting file last modified date
On dimanche 21 mai 2017 15:15:10 CEST Andrey Goreev wrote:
In the meantime, exiftool can do that easily.
exiftool -api quicktimeutc=1 "-FileModifyDate<QuickTime:CreateDate"
-overwrite_original FILE  Change QuickTime:CreateDate to whatever tag you
want to copy the info from or to a certain value (date).

But make sure you know which tag you need to overwrite...
In this case, the OP wanted to change the date the file was last /modified/.
Your exemple would change the date the file content was /created/, not the same
thing. I'd even think you wouldn't want to touch that particular item at all,
except when you know the date is wrong and you know the correct creation date.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170521/83b60105/attachment-0001.html>




Message: 3
Date: Sun, 21 May 2017 16:50:41 +0200
From: Uwe Haider <[hidden email]>
To: [hidden email]
Subject: Re: file not found.... -> no start! (Uwe Haider)
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=utf-8

Thanks Andrey,

I've tested it with vim and it works for my user. Writing is possible to
the NAS.

uhai

--
Diese Nachricht wurde mobil versendet.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RE: Re: file not found.... -> no start!

Uwe Haider
In reply to this post by Uwe Haider
Once again:

My NAS is connected via nfs. DigikamDB is mysql installed on the NAS.

This is supposed to work, just look here:

https://scribblesandsnaps.com/2011/03/13/manage-photos-from-multiple-digikam-installations/

Starting digikam in bash I can see, how digikam works with mariadb ->
The connection via nfs is no problem. The problem is, that so much files
aren't found by digikam. Is it a good idea to remove this albumpaths in
mariadb via shell? So digikam will nort seek the missing files....

--
Uwe Haider
[hidden email]
http://www.familie-haider.de


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RE: Re: file not found.... -> no start!

Gilles Caulier-4
The connection between digiKam and a remote MariaDB server work
through network socket.

So yes using a NAS to host a remote MariaDB server is safe. I have a
test server on my NAS too.

The problem is the network bootleneck. It's slow. You need a good
network, at least 1 Gb to be suitable. Here all pass through
Power-line communication network which is limite to 100 Mb, and it's
not enough.

Gilles Caulier

2017-05-25 12:11 GMT+02:00 Uwe Haider <[hidden email]>:

> Once again:
>
> My NAS is connected via nfs. DigikamDB is mysql installed on the NAS.
>
> This is supposed to work, just look here:
>
> https://scribblesandsnaps.com/2011/03/13/manage-photos-from-multiple-digikam-installations/
>
> Starting digikam in bash I can see, how digikam works with mariadb ->
> The connection via nfs is no problem. The problem is, that so much files
> aren't found by digikam. Is it a good idea to remove this albumpaths in
> mariadb via shell? So digikam will nort seek the missing files....
>
> --
> Uwe Haider
> [hidden email]
> http://www.familie-haider.de
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RE: Re: file not found.... -> no start!

AndriusWild
In reply to this post by Uwe Haider
Looking at the comments to the Dmitri's article the configuration seems to be working. I don't think network speed is an issue nowadays. Even wifi is up to 5G now.

I would look at the missing files and try to find them in file manager manually first. Maybe there is an issue with the mount point?

Sorry  I have never done anything like that myself so I cannot be of much help.



Sent from my Samsung Galaxy smartphone.

-------- Original message --------
From: Uwe Haider <[hidden email]>
Date: 2017-05-25 4:11 AM (GMT-07:00)
Subject: Re: RE: Re: file not found.... -> no start!

Once again:

My NAS is connected via nfs. DigikamDB is mysql installed on the NAS.

This is supposed to work, just look here:

https://scribblesandsnaps.com/2011/03/13/manage-photos-from-multiple-digikam-installations/

Starting digikam in bash I can see, how digikam works with mariadb ->
The connection via nfs is no problem. The problem is, that so much files
aren't found by digikam. Is it a good idea to remove this albumpaths in
mariadb via shell? So digikam will nort seek the missing files....

--
Uwe Haider
[hidden email]
http://www.familie-haider.de


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: file not found.... -> no start!

Remco Viëtor
In reply to this post by Uwe Haider
On jeudi 25 mai 2017 12:11:11 CEST Uwe Haider wrote:

> Once again:
>
> My NAS is connected via nfs. DigikamDB is mysql installed on the NAS.
>
> This is supposed to work, just look here:
>
> https://scribblesandsnaps.com/2011/03/13/manage-photos-from-multiple-digikam
> -installations/
>
> Starting digikam in bash I can see, how digikam works with mariadb ->
> The connection via nfs is no problem. The problem is, that so much files
> aren't found by digikam. Is it a good idea to remove this albumpaths in
> mariadb via shell? So digikam will nort seek the missing files....

Stupid question: the paths Digikam searches are available? E.g. you can follow
that same path in a file manager or a konsole and actually see the files there
with the /exact/ same path?

If you or Digikam don't have permission to read the image files, or one of the
directories in the path, the files will be unreadable or even invisible. And
depending on how you configure your NAS, that's fairly easy to do (or if you
forgot to  mount the NFS directories on the client system... been there, done
that).

Same effect if you have e.g. lowercase in the expected paths and uppercase in
the real paths.

Remco
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: RE: Re: file not found.... -> no start!

Uwe Haider
In reply to this post by Uwe Haider
Thanks a lot for your time and answers.

I think you missed my first email. I've lost a hard disk with an part of my collection. And I have moved on to NAS with the collection and the SQL-Server (mariadb). So a lot of pictures, folders an paths in the mariadb-tables don't exist any more (lost hdd). Starting digikam gives a bunch of error messages. I think, this messages break digikams start.

The speed of the network connection don't lead to error messages - or I haven't found them...

To avoid all the missing file errors can I drop the album paths in mariadb. This will leave a bunch of pictures in the tables without an album and an album root path. Will dk correct this tables? Or will I get much more errors doing so?
Looking at the comments to the Dmitri's article the configuration seems to be working. I don't think network speed is an issue nowadays. Even wifi is up to 5G now.
I would look at the missing files and try to find them in file manager manually first. Maybe there is an issue with the mount point?
Sorry  I have never done anything like that myself so I cannot be of much help.
The missing files are lost.
I would try to copy a large file e.g. a movie to/from NAS and watch how long it takes.  File_size / measured_time = your real speed

Ok, I will try this the next few days...
Stupid question: the paths Digikam searches are available? E.g. you can follow
that same path in a file manager or a konsole and actually see the files there 
with the /exact/ same path?

If you or Digikam don't have permission to read the image files, or one of the 
directories in the path, the files will be unreadable or even invisible. And 
depending on how you configure your NAS, that's fairly easy to do (or if you 
forgot to  mount the NFS directories on the client system... been there, done 
that).

Remco
part of my albums are lost, the folders of the NAS are still available, read/write permissions for my user are set correct. read/write works, testet with vim. I just have to clean up the SQL-tables by hand I think.... Or is there a tool?

Note : I just updated the announcement page with screenshots and a
small sction about new Geolocation Bookmark Editor.

https://www.digikam.org/news/2017-05-23-5.6.0-pre-release/

The next 5.6.0 is also postponed to 11/06/2017 to be sure to receive
enough feedback for users.

Best

Gilles Caulier

Thanks a lot for all your work Gilles.

-- 
Uwe Haider
[hidden email]
http://www.familie-haider.de
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: file not found.... -> no start!

jdd@dodin.org
Le 26/05/2017 à 19:44, Uwe Haider a écrit :

> SQL-Server (mariadb). So a lot of pictures, folders an paths in the
> mariadb-tables don't exist any more (lost hdd). Starting digikam gives a
> bunch of error messages. I think, this messages break digikams start.

did you share the error messages? (eventually starting digikam from console)

jdd
Loading...