[Digikam-devel] [Bug 124013] New: Digicam is overwhelmed by a large (60Gb) album

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From ahuggel gmx net  2006-09-07 13:24 -------
As a workaround, check the number of files that can be open at any one time and increase if necessary. See, e.g., here:

http://www.patoche.org/LTT/kernel/00000128.html

Also, if your images are RAW images, use exiv2 from svn to reduce the time needed to scan for metadata by about factor 6 compared to v0.10. For JPEGs this has no effect.

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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From ahuggel gmx net  2006-09-07 13:31 -------
Just noticed that this is an old article I referred to. These parameters have moved to /proc/sys/fs/ in the meantime.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Marcel Wiesweg]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From marcel.wiesweg gmx de  2006-09-16 17:02 -------
The problem is KDirWatch, and the number of directories.
It seems that there is a certain maximum number of directories (1024 is a good guess). The error occurs when too many directories are added to the KDirWatch instance. I think there are a various methods how KDirWatch is watching the files, and something may have changed from 3.5.2->3.5.3.
I can reproduce the problem here with > ~1000 directories, each only one file.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Arnd Baecker]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From arnd.baecker web de  2007-10-03 07:28 -------
For KDE4, is there an improved KDirWatch which would solve this bug?
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From caulier.gilles gmail com  2007-11-28 16:35 -------
Marcel,

Using more recent KDE3.5.x solve this problem ? KDirWatch have been fixed ?

If no, i recommend to affect this file on kdelibs core component. Fine for you ?

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

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From detlef jockheck de  2007-12-11 21:51 -------
Hi,
I just compiled digiKam 0.9.3-rc1 on Suse 9.3 with the hope that it is fixed in a newer version than 0.7.5 (shipped with SuSE). Can this problem be solved by using newes KDirWatch?
Detlef
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From caulier.gilles gmail com  2007-12-11 21:54 -------
Detlef,

I don't know if KDirWatch is fixed. It come from KDE API and i have no feedback from KDE developper about.

The only way is to check code or in bugzilla if something have been fixed recently...

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

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From caulier.gilles gmail com  2008-03-28 18:10 -------
Marcel,

With a recent KDE version, KDirwatch have been fixed ? If not, we need certainly to move this file in KDELibs bugzilla component, else nothing will be done.

Greg,

Are you tested with a more recent KDE ?

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marcel.wiesweg gmx de



------- Additional Comments From caulier.gilles gmail com  2008-03-28 19:01 -------
Marcel,

look in KDirWatchPrivate::addEntry() implementation. There is not limitation here:

http://websvn.kde.org/branches/KDE/3.5/kdelibs/kio/kio/kdirwatch.cpp?revision=556220&view=markup

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

[Marcel Wiesweg]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From marcel.wiesweg gmx de  2008-03-29 18:21 -------
If you look at the man page of inotify_add_watch, which is called by KDirWatch if it is using inotify, you'll see that a  file descriptor is returned. It's a good guess that there is an operating system limit on the number of open files and every watched directory counts as an open file.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From caulier.gilles gmail com  2008-03-29 19:22 -------
Marcel,

From original post, user said than Ext3 file system is used to host photos.

Greg,

I can see 2 issues to progress here :

- try to use another FS, like ReiserFS (i use it here without any problem)
- try to use FAM notificator instead inotify  (i use it here without any problem).

Can you try on your computer ?

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         
caulier.gilles gmail com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Database
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=124013         




------- Additional Comments From joerg.kuehne lycos de  2008-06-23 21:42 -------
There is a limit of maximum number of open files per process. The bash command
ulimit -Hn displays the hard limit set by root and ulimit -Sn shows the soft limit adjustable by user but not larger than the hard limit. It seems that the default value is 1024 which is not enough for digikam album path with a large number of directories.
Typically the system settings for the hard limit and the default soft limit are made in /etc/security/limits.conf (PAM configuration file)
Add the following lines
*                hard    nofile          8192
*                soft    nofile          8192
to increase the limit to 8192.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel