I remember, that this problem here was discussed here before (I think so).
Though I have unmarked 'file indexing' in KDE settings, my mounted external USB harddisk (1TByte) is busy without that I execute any program to access. To check, which program else accesses onto my harddrive I did an:
- Code: Select all
fuser -v /media/*
USER PID ACCESS COMMAND
/run/media/linuxfluesterer/Toshiba-1TB-jfs:
root kernel mount /run/media/richard/Toshiba-1TB-jfs
linuxfluesterer 4803 f.... nepomukfilewatc
which tells me, nepomukfilewatch accesses my hard drive. To check more, I did a:
- Code: Select all
lsof|grep nepomukfil
nepomukfi 4803 linuxfluesterer txt REG 8,1 160160 134948355 /usr/bin/nepomukfilewatch
nepomukfi 4803 linuxfluesterer mem REG 8,1 1686 205977895 /usr/share/locale/de/LC_MESSAGES/nepomukfilewatch.mo
QThread 4803 4815 linuxfluesterer txt REG 8,1 160160 134948355 /usr/bin/nepomukfilewatch
QThread 4803 4815 linuxfluesterer mem REG 8,1 1686 205977895 /usr/share/locale/de/LC_MESSAGES/nepomukfilewatch.mo
QProcessM 4803 4816 linuxfluesterer txt REG 8,1 160160 134948355 /usr/bin/nepomukfilewatch
QProcessM 4803 4816 linuxfluesterer mem REG 8,1 1686 205977895 /usr/share/locale/de/LC_MESSAGES/nepomukfilewatch.mo
QInotifyF 4803 4820 linuxfluesterer txt REG 8,1 160160 134948355 /usr/bin/nepomukfilewatch
QInotifyF 4803 4820 linuxfluesterer mem REG 8,1 1686 205977895 /usr/share/locale/de/LC_MESSAGES/nepomukfilewatch.mo
nepomukfi 4804 linuxfluesterer txt REG 8,1 172920 134948354 /usr/bin/nepomukfileindexer
nepomukfi 4804 linuxfluesterer mem REG 8,1 2608 205977894 /usr/share/locale/de/LC_MESSAGES/nepomukfileindexer.mo
QInotifyF 4804 4824 linuxfluesterer txt REG 8,1 172920 134948354 /usr/bin/nepomukfileindexer
QInotifyF 4804 4824 linuxfluesterer mem REG 8,1 2608 205977894 /usr/share/locale/de/LC_MESSAGES/nepomukfileindexer.mo
QProcessM 4804 4826 linuxfluesterer txt REG 8,1 172920 134948354 /usr/bin/nepomukfileindexer
QProcessM 4804 4826 linuxfluesterer mem REG 8,1 2608 205977894 /usr/share/locale/de/LC_MESSAGES/nepomukfileindexer.mo
and receive a long list for an explicitely excluded external drive from indexing. So, why?
I want nepomukfileindexer for my build in partitions, that's ok, but I have many unmounting problems when this program accesses my external harddrive. I often could not mount that drive again, because I got an error, so that I had to do a fsck '/dev/sdb1'.
Is this still a (recurring) bug? Btw, while I wrote this here, my drive is busy all the time (flashing light).
Thank you for any idea.
-Linuxfluesterer (I love KDE ...)
Sabayon 13.10 64bit, KDE 4.11.1, Kernel 3.11.2
