Apple Event: May 7th at 7 am PT
I would like to know why the process mtmd is using 180% of the cpu after i installed Lion
And also the mdworker is running at 100%
This cant be right. can it?
MacBook Pro, Mac OS X (10.7)
I think I can confirm the problem lies with the mds and mdworker process.
Even when I turn off Time Machine. It will still keep running
The CPU usage of mds will keep getting bigger until I decide to restart.
I have spotted the process at 65% CPU usage.
mds (MetaData Server) is used mostly by Spotlight to index your stuff.
If there's a tiny dot in the Spotlight icon at the right of your menubar, click it. It will show a progress bar (or bars) showing what it's doing. That will slow down pretty much everything.
Yes, I know mds is a spotlight process for indexing my harddrive.
But its already done indexing. I have been working with lion for a week now.
So there is no tiny dot in the Spotlight icon.
The problem is that when i turn on my Time Machine.
The mds will start going crazy again.
I think mds is trying to index my Time Capsule.
Or its in conflict with whatever Time Machine is doing.
But I can't be sure.
Of course I tried including the Time Capsule harddrive in the spotlight blacklist.
So it will not index the harddrive.
But because the harddrive is automatically unmounted when Time Machine is done.
It will be removed from the blacklist.
ivandsfromamsterdam wrote:
. . .
I think mds is trying to index my Time Capsule.
Yes, exactly. I have no idea why perfectly good backups from Snow Leopard have to be re-indexed, but they do.
And you cannot prevent it by putting them in the Spotlight exclusion list; you get a message that the backups will be indexed, but it will omit anything else on the volume. (That's always been the case; it just didn't put up a message before).
If the index is corrupted, it could explain what's happening. Try deleting it from the disk image.
Pondini wrote:
If the index is corrupted, it could explain what's happening. Try deleting it from the disk image.
How would i delete a corrupted index?
I hope u dont mean deleting my backups.
ivandsfromamsterdam wrote:
. . .
How would i delete a corrupted index?
I hope u dont mean deleting my backups.
That's the easy way. 😉
The hard way is, first download the Tinker Tool app, per #A3 in Time Machine - Troubleshooting. That will show invisible files.
Then via the Finder, locate the sparse bundle, and double-click it to mount the disk image inside it. It will appear on your desktop or Finder sidebar, and is named "Time Machine Backups."
Double-click it to open it. Inside it you'll find a .Spotlight-V100 folder. Delete it (you'll have to enter your Admin password), and empty the trash. Do not touch anything else.
Eject the disk image, and run a backup. The first one will take quite a while, as it must be indexed, but thereafter, backups should run normally.
Could the Spotless 3rd party utility be used to remove index? I just got the utility recently but have not played with it much. Is there a GUI interface for Spotlight in Lion?
Roosevelt Jones wrote:
Could the Spotless 3rd party utility be used to remove index? I just got the utility recently but have not played with it much.
I don't use it, but it's doubtful.
Is there a GUI interface for Spotlight in Lion?
For any other use, yes, you can place a drive (or whatever) in the System Prefs > Spotlight > Privacy panel momentarily, then remove it. But that doesn't on Time Machine backups.
If your backups are on an external HD, you won't have a sparse bundle as in the previous post. Instead, the index will be at the top level of the TM drive.
Do yo know if there is a preference (or other means) to permanently disable local snapshots? Apparently they get automatically re-enabled when cycling TimeMachine off-on.
Thank you in advance!
See #30 in Time Machine - Frequently Asked Questions.
Thank you for your quick answer. However, using tmutil is only a temporary solution. In the moment you swithch Time Machine off and on again for any reasons, local snapshots resume. And unfortunately Lion GM / Release lacks the Disable Local Snapshots option in Time Machine Setup. I was hoping for a way to *permanently* disable local snapshots. I think it is a questionable feature anyways (as you also said in your FAQ #30) and for me it is beyond anoying.
Thanks again.
All true. 😟
The workaround is, don't turn TM off. If you don't want backups for a while (like while doing an OSX update, or rearranging a bunch of large folders), just eject the drive.
But most of the time, they won't cause a real problem, as they'll be deleted after a few days, or if your disk gets too full.
I did a little research: /Library/Preferences/com.apple.TimeMachine.plist has a boolean property "MobileBackups" which hardcodedly defaults to "YES" on portable machines. That is sort-of ok (however, it should be controllable from the Time Machine Preference Pane...). What is NOT ok (IMHO) is that it flippes back to YES after TM restart, even though if it had been set to NO before, manually or via tmutil disablelocal. This is clearly a bug in my oppinion.
manfred_k wrote:
I did a little research: /Library/Preferences/com.apple.TimeMachine.plist has a boolean property "MobileBackups" which hardcodedly defaults to "YES" on portable machines. That is sort-of ok (however, it should be controllable from the Time Machine Preference Pane...). What is NOT ok (IMHO) is that it flippes back to YES after TM restart, even though if it had been set to NO before, manually or via tmutil disablelocal. This is clearly a bug in my oppinion.
Actually, it's not a bug; it's worse: it's designed that way. 😮
In the early beta versions of Lion, there was a separate checkbox on the TM Prefs > Options panel to control whether Local snapshots were made. When it was removed, Apple told us to use tmutil to turn them off instead.
By all means, provide your opinion here: http://www.apple.com/feedback/timemachine.html
same problem
timemashine backup on external harddrive
MacBookPro 2009 version
with a 2.8 GHz Intel Core 2 Duo
and 4 Gb of ram
please public fix update!
os x lion mtmd
