0

I have laucned one week ago the following command : sudo mddutil -E / to reindex all my volume (from root /).

Unfortunately, it seems that mdworker.shared continue to run but I can't explain their status : they seem to be sleeped since letter 'S' when I do a 'ps aux | grep mdworker' :

For example :

    _spotlight       20708   0.0  0.1  6421412  44116   ??  S    12:38PM   0:00.11 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker_shared -s mdworker -c MDSImporterWorker -m com.apple.mdworker.shared
    _spotlight       20707   0.0  0.1  6544284  39320   ??  S    12:38PM   0:00.11 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker_shared -s mdworker -c MDSImporterWorker -m com.apple.mdworker.shared
    _spotlight       20705   0.0  0.1  6159268  41084   ??  S    12:38PM   0:00.11 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework/Versions/A/Support/mdworker_shared -s mdworker -c MDSImporterWorker -m com.apple.mdworker.shared

etc...

I understand that redindexing is said to be very long, especially since I have a 2 TB storage volume but on the other side, the command 'mdutil -E /' has been launched 1 week ago.

How can I deal with these sleeping processes ? What to do to "reactivate them' ?

I saw there was a problem when I used classical locate command to make a test on the research of files and where locate has found a file, mdfind failed to find it :

$ /usr/bin/locate 154.46

SUM_GCsp_XC_AND_GCsp_NO_XC_MATRIX_33x33_Respectively_Fom_571.35_AND_154.46.py

whereas :

mdfind -name 154.46 returns nothing and mdfind 154.46 returns results which don't contain the substring 154.46 into filename (maybe it looks inside files without -name option ?)

Any help/suggestion/track is welcome.

You must log in to answer this question.

Browse other questions tagged .