Spotlight + Time Machine woes - tried everything...

I have a 10.6.7 system with a 1 Tb internal drive (~700 Gigs of it used) and an eSATA external drive used as a TM destination. I make backups religiously, and I'm up-to-date with all the updates. I have a similar setup at home, with mostly the same data, which doesn't have the following problem, so I know it *can* work (and should!). But here's what I have.
This all started after exporting a bunch of old emails as individual files (~30 Gigs-worth - maybe 20,000 files all in all). I noticed that my Time Machine is taking forever to make backups. Not just the first time, but all the time, even when no files have changed (at least, at the user level). I've repaired both disks with Disk Utility, reset TM according to the suggestions in the TM forum, and started from scratch with a blank drive. The problem is this, as seen in Time Buddy:
Starting standard backup
Backing up to: /Volumes/Mercury External Drive/Backups.backupdb
No pre-backup thinning needed: 989.3 MB requested (including padding), 341.04 GB available
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Indexer unavailable (200)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Indexer unavailable (200)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
     The TM often tries for like 30-40 minutes (each hour!) and then sometimes fails with
Error: Flushing index to disk returned an error: 0
Copied 3725 files (167.0 MB) from volume Raptor RAID0.
Backup canceled.
     I don't think it's a hardware problem with the drive because this used to happen when my drive was a USB2 drive (I specifically got a new eSATA drive because I thought the extra speed might help).
    The problem seems to be that the Spotlight indexer is constantly busy. I followed directions to completely wipe out and rebuild the Spotlight (and this is after using SuperDuper to clone my drive to a completely clean disk, and using Cache Cleaner to do a deep cache wipe etc.).  The Spotlight rebuild took 2 days, and during this time the size of the .Spotlight... file went up and down. The time predicted by the little magnifying glass thing up in the menu bar went from 8 hours to 657 hours, but eventually it finished (when I excluded the folder of exported mail messages via privacy list). I already have the TM and other disks excluded from Spotlight.
    Spotlight alternates between being quiet and usable (no dot in the magnifying glass) and mds alternating between 98% and 5% in the "top" terminal command, and all of a sudden running like crazy (dot in the magnifying glass) with a spinning barberpole and no estimate of finishing, for no apparent reason.
    I've used fs_usage in terminal to determine that Spotlight was spending a lot of time on my Microsoft Entourage files, so I excluded those. Unfortunately I need it to scan my Microsoft Outlook 2011 files because I can't search for emails without it (yes, I'd love to dump the Microsoft product but I can't for now).  Now the fs_usage doesn't work anymore - it says
fs_usage: the trace facility is currently in use...
                fs_usage, sc_usage, and latency use this feature.
a reboot helps, but only for a few minutes - then fs_usage says "killed" and won't restart again (giving the above message).
   I'm at the end of my rope. What do I do? I need my disk indexed by Spotlight, and I need TM to be able to do its normal 3-second/hour backups after the initial one.   Where do I go next?   Is it possible that I simply have too many files here for Spotlight to work properly?
thanks in advance,
Mike

Yes, I did mean GUID. It was the TM drive. I did an archive and install, but keep in mind this was a brand new computer, that had a fresh install. Also, this all worked on the older system. I would try an erase and install, but i'd like to see if there is anything else to try first.
Just ran again, the freeze didnt happen but it did call out some random garageband instrument.
Backup requested by user
Starting standard backup
Backing up to: /Volumes/Time Machine/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 68.0 GB excluded items size: 44.1 MB for volume Macintosh HD
No pre-backup thinning needed: 81.50 GB requested (including padding), 90.43 GB available
Waiting for index to be ready (904 > 0)
Error: (-36) SrcErr:NO Copying /Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples/VI1SHDT C6-.wav to /Volumes/Time Machine/Backups.backupdb/Michael DiMaria’s MacBook Pro/2008-10-18-104514.inProgress/943A6BE5-1166-478F-8CD8-E5454EEB7F11/Macintosh HD/Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples
Stopping backup.
Error: (-8062) SrcErr:NO Copying /Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples/VI1SHDT C6-.wav to /Volumes/Time Machine/Backups.backupdb/Michael DiMaria’s MacBook Pro/2008-10-18-104514.inProgress/943A6BE5-1166-478F-8CD8-E5454EEB7F11/Macintosh HD/Library/Application Support/GarageBand/Instrument Library/Sampler/Sampler Files/Boldt Ensemble Detatche.Samples
Copied 1880 files (5.5 GB) from volume Macintosh HD.
Copy stage failed with error:11
Backup failed with error: 11

Similar Messages

  • Time Machine trouble, tried everything !

    Hi,
    I have a Mac OSc Version 10.7.5, with 2.5 Ghz Intel Core i5, with a hard drive that is 500 GB, i"ve used 180.73 and have 318.52 free space.  I'm trying to do a backup using Time Machine using a 3TB, Seagate Desktop External Hard Drive USB 3.0.  I keep getting the following error message, and neither Seagate nor Apple Tech Support can figure it out.
    Can anyone help ?

    Sorry about that.
    Not your fault. The screenshot is showing now. The forum software is quite unreliable lately.
    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Post the messages timestamped from then until the end of the backup, or the end of the log if that's not clear.
    Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into a message.
    Some personal information, such as the names of your files, may be included — edit that out, too, but don’t remove the context.

  • Re Time Machine I have an external  hard drive with files I backed up manually over the past 2 years 1TB of memory. I am finally taking the leap to use Time machine to back everything.   will I have to reformat that drive, thus wiping my previous bac

    Re Time Machine
    I have an external  hard drive with files I backed up manually over the past 2 years 1TB of memory.
    I am finally taking the leap to use Time machine to back everything.
    will I have to reformat that drive, thus wiping my previous back ups?
    can I split it the drive in two partitions?
    Also
    as I have two separate Macbook Pro's- one older than the other.
    OSX 10.68
    the other is
    OSX 10.75
    can I back them up separately?
    or even synch and merge files and folders etc? between the two?

    You CAN use a drive with files already on it to store Time Machine backups. But long term, that is not recommended. You do not need to reformat or re-partition the drive to do this. Once Time Machine Backups are established, you could remove the old files.
    But do not delete Time Machines files with the Finder -- that can cause it to lose its place and lose everything.
    With the cost of backup drives under US$100, it might be a better idea in the long run to get another drive. Best results from Time Machine is a drive about 3 times larger than the drive(s) you are backing up.

  • I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

    I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?

    It must have found the old backup corrupt.. so you will more than likely have little choice. You can archive off the old backup if it is still useful.
    You can also verify it. See A5 http://pondini.org/TM/Troubleshooting.html
    He also has some info on this problem. eg C13.

  • HT203177 I had to get a new hard drive in my 27 in IMac. I used time machine to get everything back on my computer. I just turn on time machine and its says it's preparing over 800,000 items to back-up, it never back-up, it stop and starts the process ove

    I had to get a new hard drive in my 27 in IMac. I used time machine to get everything back on my computer. I just turn on time machine and its says it's preparing over 800,000 items to back-up, it never back-up, it stop and starts the process over again.

    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
    *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
    3. Click the First Aid tab.
    4. Select your Mac OS X volume.
    5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then repair the backup/TM drive.

  • HT3275 2 problems: All files are locked - how to globally unlock on the backup drive? I am backing up large video files 500GB on a 2 TB machine. Time Machine repeatedly copies everything using up all of disk space. I only need 1 copy not, twenty. What to

    2 problems: All files are locked - how to globally unlock on the backup drive? I am backing up large video files 500GB on a 2 TB machine. Time Machine repeatedly copies everything using up all of disk space. I only need 1 copy not, twenty. What to do?

    2 problems: All files are locked - how to globally unlock on the backup drive? I am backing up large video files 500GB on a 2 TB machine. Time Machine repeatedly copies everything using up all of disk space. I only need 1 copy not, twenty. What to do?

  • HT3275 Im getting the following error message when Time Machine is trying to backup:  backup disc image/volumes/data/mycomputer.sparsebundle is already in use, how do I correct?

    Im getting the following error message when Time Machine is trying to back up:  backup disc image/volumes/data/my computer.sprasebundle is already in use.  What does this mean?  How do i correct?  Thanks!

    90% of the time, all you need to do is power off the Time Capsule, wait a few minutes, and power it back up.
    If no luck, then go to the more sophisticated fixes in the link above.

  • I have been unable to retrieve emails from my external disk.  I entered the Time Machine and tried to go to April 2013, but could not find emails.  I have Lion OS X 10.7.5 .Thanks!

    I have been unable to retrieve emails from my external disk.  I entered the Time Machine and tried to go to April 2013, but could not find emails.  I have Lion OS X 10.7.5 .Thanks!
    Cecilia

    I have been unable to retrieve emails from my external disk.  I entered the Time Machine and tried to go to April 2013, but could not find emails.  I have Lion OS X 10.7.5 .Thanks!
    Cecilia

  • Spotlight does NOT work - tried EVERYTHING

    Running older Intel Mac Pro... Mountain Lion
    Spotlight just stopped working - it returns nothing but webpage suggestions.
    There are NO disks added under the Spotlight System Preferences.
    Trying to add and then remove only results in the "Privacy List Error The item couldn't be addred because you don't have the appropriate permissions.
    I've rebuilt permissions. No go.
    I've killed SystemUIServer in Activities Monitor - nada.
    I've used the info here on How to Disable (or Enable) Spotlight in Mac OS X Lion which includes the terminal commands for killing Spotlight, restarting again, and forcing reindexing. Nothing. Well almost nothing- I got it to re-index for a bit last night... But when you use Spotlight.... nothing.
    I have an ugly suspicion it has to do with perceived ownership of the disks by the OS  - anyone care to take me up on this? Here's why:
    I you reveal the hidden files you see this:
    When I "Get Info" (Command-I) I see these permissions... the disk first, and then the .Spotlight-V100 folder:
    So why does the .Spotlight-V100 say that everyone has "No Access"? But looking at my Mac Mini these settings seem to be correct.
    I tried changing ownership on the everyone to "Read" (which didn't work everytime I tried until I started writing this of course) but it just returns the same Privacy Access error when you try to add the disk to the Spotlight Preferences Privacy list again. I tried changing it to Read & Write... same thing.
    Now inside the Spotlight-V100 folder is the VolumeConfiguration.plist file - I'm wondering if something in these preferences (which you can read unless you change the setting to "Read" where it is first set 'everyone' as 'no access') might give a clue - so here is the content of that file and I'll leave this for now to see if anyone has any clue what's going on here. Thanks
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
              <key>Annotations</key>
              <dict>
                        <key>Creation_Predicates</key>
                        <dict>
                                  <key>false</key>
                                  <false/>
                                  <key>fstype.hfs</key>
                                  <true/>
                                  <key>interconnect.sata</key>
                                  <true/>
                                  <key>is.alreadyindexed</key>
                                  <false/>
                                  <key>is.automount</key>
                                  <false/>
                                  <key>is.backupstore</key>
                                  <false/>
                                  <key>is.backupvolume</key>
                                  <false/>
                                  <key>is.bootablevolume</key>
                                  <true/>
                                  <key>is.cameramedia</key>
                                  <false/>
                                  <key>is.diskimage</key>
                                  <false/>
                                  <key>is.dontbrowse</key>
                                  <false/>
                                  <key>is.ejectable</key>
                                  <false/>
                                  <key>is.external</key>
                                  <false/>
                                  <key>is.externalvolumes.defaultoff</key>
                                  <false/>
                                  <key>is.externalvolumes.ignore</key>
                                  <false/>
                                  <key>is.filevault</key>
                                  <false/>
                                  <key>is.forcedefaultindex</key>
                                  <false/>
                                  <key>is.forcefsonly</key>
                                  <false/>
                                  <key>is.home</key>
                                  <false/>
                                  <key>is.internal</key>
                                  <true/>
                                  <key>is.ipod</key>
                                  <false/>
                                  <key>is.local</key>
                                  <true/>
                                  <key>is.lowdiskspace</key>
                                  <false/>
                                  <key>is.mirrored.idisk</key>
                                  <false/>
                                  <key>is.mobilebackups</key>
                                  <false/>
                                  <key>is.network</key>
                                  <false/>
                                  <key>is.quarantined</key>
                                  <false/>
                                  <key>is.readonly</key>
                                  <false/>
                                  <key>is.removable</key>
                                  <false/>
                                  <key>is.rootfs</key>
                                  <true/>
                                  <key>is.safeboot</key>
                                  <false/>
                                  <key>is.syntheticmount</key>
                                  <false/>
                                  <key>is.tinyvolume</key>
                                  <false/>
                                  <key>is.windowsbootablevolume</key>
                                  <false/>
                                  <key>is.xsan</key>
                                  <false/>
                                  <key>policy.location.volume</key>
                                  <true/>
                                  <key>self.appleinternal</key>
                                  <false/>
                                  <key>self.server</key>
                                  <false/>
                                  <key>status.neverindex</key>
                                  <false/>
                                  <key>supports.catsearch</key>
                                  <true/>
                                  <key>supports.fileids</key>
                                  <true/>
                                  <key>supports.volfs</key>
                                  <true/>
                                  <key>true</key>
                                  <true/>
                                  <key>uuid.b449cee2-6ad5-3b8a-a749-9e6d14c278b1</key>
                                  <true/>
                        </dict>
                        <key>DefaultStore_EffectiveSearch</key>
                        <integer>3</integer>
                        <key>DefaultStore_RequestedSearch</key>
                        <integer>3</integer>
              </dict>
              <key>ConfigurationCreationDate</key>
              <date>2013-02-15T00:07:09Z</date>
              <key>ConfigurationCreationVersion</key>
              <string>Version 10.8.2 (Build 12C60)</string>
              <key>ConfigurationModificationDate</key>
              <date>2013-02-15T00:07:09Z</date>
              <key>ConfigurationModificationVersion</key>
              <string>Version 10.8.2 (Build 12C60)</string>
              <key>Exclusions</key>
              <array/>
              <key>Options</key>
              <dict>
                        <key>ConfigurationType</key>
                        <string>Default</string>
              </dict>
              <key>Stores</key>
              <dict>
                        <key>7577F89E-857D-4CB6-B9D0-E937F1944380</key>
                        <dict>
                                  <key>CreationDate</key>
                                  <date>2013-02-15T00:07:09Z</date>
                                  <key>CreationVersion</key>
                                  <string>Version 10.8.2 (Build 12C60)</string>
                                  <key>IndexVersion</key>
                                  <integer>95</integer>
                                  <key>PartialPath</key>
                                  <string>/</string>
                                  <key>PolicyDate</key>
                                  <date>2013-02-15T00:07:09Z</date>
                                  <key>PolicyLevel</key>
                                  <string>kMDConfigSearchLevelReadWrite</string>
                                  <key>PolicyVersion</key>
                                  <string>Version 10.8.2 (Build 12C60)</string>
                        </dict>
              </dict>
    </dict>
    </plist>

    Hi Linc,
    Thanks for picking up my thread and offering your insights.
    Going to Console and filtering for mdworker reveals no entries what so ever. I recognize mdworker as one of the key  components of Spotlight so suggests it's not running. I also see that Console is posting repeated crashes for for
    LaunchServices/5123589
    here's the full entry:
    2/15/13 8:28:20.942 PM ReportCrash[637]: failed looking up LS service ( scCreateSystemService returned MACH_PORT_NULL, called from SetupCoreApplicationServicesCommunicationPort, so using client-side NULL calls.
    2/15/13 8:28:20.942 PM ReportCrash[637]: LaunchServices/5123589: Unable to lookup coreservices session port for session 0x186a0 uid=0 euid=0
    2/15/13 8:28:20.998 PM com.apple.launchd[1]: (com.apple.metadata.mds[640]) Job appears to have crashed: Segmentation fault: 11
    2/15/13 8:28:20.998 PM com.apple.launchd[1]: (com.apple.metadata.mds) Throttling respawn: Will start in 10 seconds
    2/15/13 8:28:21.107 PM ReportCrash[637]: Saved crash report for mds[640] version 707.3 to /Library/Logs/DiagnosticReports/mds_2013-02-15-202821_COMPUTER_NAME.crash
    this certainly appears also to be Spotlight because running this in Terminal...
    sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
    and the crash reports stop. Run this to reload Spotlight...
    sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.metadata.mds.plist
    and the errors start again.
    This is the crash report noted above - pretty sure this is what you want now - I see no mdsworker but mds errors all through...
    Thoughts?
    Thanks.
    Process:         mds [640]
    Path:            /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Support/mds
    Identifier:      mds
    Version:         707.3
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [1]
    User ID:         0
    Date/Time:       2013-02-15 20:28:20.498 -0500
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Crashed Thread:  9  Dispatch queue: <MDSDiskStore 0x7fd02500ac00 shutdown:NO got shutdown notification:NO>
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
    VM Regions Near 0x8:
    -->
        __TEXT                 000000010514c000-000000010526c000 [ 1152K] r-x/rwx SM=COW  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Support/mds
    Application Specific Information:
    [0x105b70000](Error) IndexGeneral in ssize_t fd_pread(fd_ptr, void *, size_t, off_t):pread(-1 , o:0, s:0) err:2
    [0x105b70000](Error) IndexCI in _Bool store_stream_init(store_stream_t *, fd_ptr, _Bool):store_stream_init err:2
    [0x105b70000](Warning) IndexStore in int db_restore_dirty_chunk_info(int, db_dirty_chunk_info *):Restore error: 2, recovering from shadow
    [0x105b70000](Error) IndexState in int _SIOpenIndexFilesWithState(SIRef, uint32_t, _Bool, _Bool, _Bool, _Bool *, DocID *, CIDocCounts *):ContentInde
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib                  0x00007fff86abe686 mach_msg_trap + 10
    1   libsystem_kernel.dylib                  0x00007fff86abdc42 mach_msg + 70
    2   com.apple.CoreFoundation                0x00007fff84b22803 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation                0x00007fff84b27ee6 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation                0x00007fff84b276b2 CFRunLoopRunSpecific + 290
    5   mds                                     0x000000010515aa54 0x10514c000 + 59988
    6   libdyld.dylib                           0x00007fff8a4327e1 start + 1
    Thread 1:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 2:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x00007fff86ac0d16 kevent + 10
    1   libdispatch.dylib                       0x00007fff8d81ddea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib                       0x00007fff8d81d9ee _dispatch_mgr_thread + 54
    Thread 3:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 4:: Dispatch queue: <MDSDiskStore 0x7fd026826400 shutdown:NO got shutdown notification:NO>
    0   libsystem_kernel.dylib                  0x00007fff86ac0ae6 fsync + 10
    1   com.apple.spotlight.index               0x000000010537b38b fd_sync + 381
    2   com.apple.spotlight.index               0x00000001053a71d8 _CIMetaInfoSync + 157
    3   com.apple.spotlight.index               0x00000001053a73ad CIMetaInfoCreate + 377
    4   com.apple.spotlight.index               0x00000001052dfbaa SICreateNewIndex + 1106
    5   mds                                     0x0000000105182318 0x10514c000 + 221976
    6   mds                                     0x0000000105181a7a 0x10514c000 + 219770
    7   mds                                     0x0000000105173868 0x10514c000 + 161896
    8   mds                                     0x00000001051cd47e 0x10514c000 + 529534
    9   mds                                     0x00000001051b4962 0x10514c000 + 428386
    10  mds                                     0x00000001051b4b21 0x10514c000 + 428833
    11  libdispatch.dylib                       0x00007fff8d81b0b6 _dispatch_client_callout + 8
    12  libdispatch.dylib                       0x00007fff8d81c47f _dispatch_queue_drain + 235
    13  libdispatch.dylib                       0x00007fff8d81c2f1 _dispatch_queue_invoke + 52
    14  libdispatch.dylib                       0x00007fff8d81c1c3 _dispatch_worker_thread2 + 249
    15  libsystem_c.dylib                       0x00007fff85029cab _pthread_wqthread + 404
    16  libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 7:
    0   libsystem_kernel.dylib                  0x00007fff86ac0ffa read + 10
    1   mds                                     0x0000000105155ced 0x10514c000 + 40173
    2   libsystem_c.dylib                       0x00007fff85027742 _pthread_start + 327
    3   libsystem_c.dylib                       0x00007fff85014181 thread_start + 13
    Thread 8:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 9 Crashed:: Dispatch queue: <MDSDiskStore 0x7fd02500ac00 shutdown:NO got shutdown notification:NO>
    0   com.apple.spotlight.index               0x00000001052ecffc SISetTransactionCount + 212
    1   mds                                     0x00000001051f951f 0x10514c000 + 709919
    2   mds                                     0x00000001051fa08f 0x10514c000 + 712847
    3   mds                                     0x0000000105172b82 0x10514c000 + 158594
    4   mds                                     0x0000000105181eb1 0x10514c000 + 220849
    5   mds                                     0x0000000105173868 0x10514c000 + 161896
    6   mds                                     0x00000001051cd47e 0x10514c000 + 529534
    7   mds                                     0x00000001051b4962 0x10514c000 + 428386
    8   mds                                     0x00000001051b4b21 0x10514c000 + 428833
    9   libdispatch.dylib                       0x00007fff8d81b0b6 _dispatch_client_callout + 8
    10  libdispatch.dylib                       0x00007fff8d81c47f _dispatch_queue_drain + 235
    11  libdispatch.dylib                       0x00007fff8d81c2f1 _dispatch_queue_invoke + 52
    12  libdispatch.dylib                       0x00007fff8d81c1c3 _dispatch_worker_thread2 + 249
    13  libsystem_c.dylib                       0x00007fff85029cab _pthread_wqthread + 404
    14  libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 10:: Dispatch queue: <MDSDiskStore 0x7fd026820400 shutdown:NO got shutdown notification:NO>
    0   libsystem_kernel.dylib                  0x00007fff86abfb26 __fcntl + 10
    1   libsystem_kernel.dylib                  0x00007fff86abf0cb fcntl + 232
    2   com.apple.spotlight.index               0x000000010537b303 fd_sync + 245
    3   com.apple.spotlight.index               0x00000001054164f7 dirty_datastore_locked + 263
    4   com.apple.spotlight.index               0x000000010541e025 add_dirty_chunk + 195
    5   com.apple.spotlight.index               0x0000000105417b48 page_alloc + 290
    6   com.apple.spotlight.index               0x0000000105417987 db2_store_obj + 325
    7   com.apple.spotlight.index               0x00000001052d730d si_create_indexmetadata + 213
    8   com.apple.spotlight.index               0x00000001052e5933 SIInitIndex + 15244
    9   com.apple.spotlight.index               0x00000001052e0bc2 SICreateNewIndex + 5226
    10  mds                                     0x0000000105182318 0x10514c000 + 221976
    11  mds                                     0x0000000105181a7a 0x10514c000 + 219770
    12  mds                                     0x0000000105173868 0x10514c000 + 161896
    13  mds                                     0x00000001051cd47e 0x10514c000 + 529534
    14  mds                                     0x00000001051b4962 0x10514c000 + 428386
    15  mds                                     0x00000001051b4b21 0x10514c000 + 428833
    16  libdispatch.dylib                       0x00007fff8d81b0b6 _dispatch_client_callout + 8
    17  libdispatch.dylib                       0x00007fff8d81c47f _dispatch_queue_drain + 235
    18  libdispatch.dylib                       0x00007fff8d81c2f1 _dispatch_queue_invoke + 52
    19  libdispatch.dylib                       0x00007fff8d81c1c3 _dispatch_worker_thread2 + 249
    20  libsystem_c.dylib                       0x00007fff85029cab _pthread_wqthread + 404
    21  libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 11:: Dispatch queue: <MDSDiskStore 0x7fd027807a00 shutdown:NO got shutdown notification:NO>
    0   libsystem_kernel.dylib                  0x00007fff86ac0fbe pwrite + 10
    1   com.apple.spotlight.index               0x00000001053a6f02 _copyFile + 981
    2   com.apple.spotlight.index               0x00000001053a70f4 copyFile + 12
    3   com.apple.spotlight.index               0x000000010541213d db2_update_datastore_state + 163
    4   com.apple.spotlight.index               0x00000001052dde36 _SIOpenIndex + 3670
    5   com.apple.spotlight.index               0x00000001052e0ea8 SIOpenIndex + 282
    6   mds                                     0x0000000105182396 0x10514c000 + 222102
    7   mds                                     0x0000000105181854 0x10514c000 + 219220
    8   mds                                     0x0000000105173868 0x10514c000 + 161896
    9   mds                                     0x00000001051cd47e 0x10514c000 + 529534
    10  mds                                     0x00000001051b4962 0x10514c000 + 428386
    11  mds                                     0x00000001051b4b21 0x10514c000 + 428833
    12  libdispatch.dylib                       0x00007fff8d81b0b6 _dispatch_client_callout + 8
    13  libdispatch.dylib                       0x00007fff8d81c47f _dispatch_queue_drain + 235
    14  libdispatch.dylib                       0x00007fff8d81c2f1 _dispatch_queue_invoke + 52
    15  libdispatch.dylib                       0x00007fff8d81c1c3 _dispatch_worker_thread2 + 249
    16  libsystem_c.dylib                       0x00007fff85029cab _pthread_wqthread + 404
    17  libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 12:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 13:: Dispatch queue: <MDSDiskStore 0x7fd02300ee00 shutdown:NO got shutdown notification:NO>
    0   libsystem_kernel.dylib                  0x00007fff86ac0fbe pwrite + 10
    1   com.apple.spotlight.index               0x00000001053a6f02 _copyFile + 981
    2   com.apple.spotlight.index               0x00000001053a70f4 copyFile + 12
    3   com.apple.spotlight.index               0x000000010541213d db2_update_datastore_state + 163
    4   com.apple.spotlight.index               0x00000001052dde36 _SIOpenIndex + 3670
    5   com.apple.spotlight.index               0x00000001052e0ea8 SIOpenIndex + 282
    6   mds                                     0x0000000105182396 0x10514c000 + 222102
    7   mds                                     0x0000000105181854 0x10514c000 + 219220
    8   mds                                     0x0000000105173868 0x10514c000 + 161896
    9   mds                                     0x00000001051cd47e 0x10514c000 + 529534
    10  mds                                     0x00000001051b4962 0x10514c000 + 428386
    11  mds                                     0x00000001051b4b21 0x10514c000 + 428833
    12  libdispatch.dylib                       0x00007fff8d81b0b6 _dispatch_client_callout + 8
    13  libdispatch.dylib                       0x00007fff8d81c47f _dispatch_queue_drain + 235
    14  libdispatch.dylib                       0x00007fff8d81c2f1 _dispatch_queue_invoke + 52
    15  libdispatch.dylib                       0x00007fff8d81c1c3 _dispatch_worker_thread2 + 249
    16  libsystem_c.dylib                       0x00007fff85029cab _pthread_wqthread + 404
    17  libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 14:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 15:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 16:
    0   libsystem_kernel.dylib                  0x00007fff86ac06d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x00007fff85029eec _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x00007fff85029cb3 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x00007fff85014171 start_wqthread + 13
    Thread 9 crashed with X86 Thread State (64-bit):
      rax: 0x00000000ffffffff  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000082
      rdi: 0x00007fd022829e00  rsi: 0x0000000000000001  rbp: 0x0000000105b6dfd0  rsp: 0x0000000105b6df50
       r8: 0x0000000000000024   r9: 0x0000000000000000  r10: 0x00000001054b2ae8  r11: 0x00000001052ecf28
      r12: 0x0000000000000100  r13: 0x0000000000000001  r14: 0x00007fd022829e00  r15: 0x00007fd022848c00
      rip: 0x00000001052ecffc  rfl: 0x0000000000010246  cr2: 0x0000000000000008
    Logical CPU: 0
    External Modification Summary:
      Calls made by other processes targeting this process:
        task_for_pid: 1
        thread_create: 0
        thread_set_state: 0
      Calls made by this process:
        task_for_pid: 0
        thread_create: 0
        thread_set_state: 0
      Calls made by all processes on this machine:
        task_for_pid: 308
        thread_create: 0
        thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=147.5M resident=115.1M(78%) swapped_out_or_unallocated=32.4M(22%)
    Writable regions: Total=174.9M written=6084K(3%) resident=7420K(4%) swapped_out=0K(0%) unallocated=167.7M(96%)
    REGION TYPE                      VIRTUAL
    ===========                      =======
    MALLOC                            127.8M
    MALLOC guard page                    80K
    Memory tag=241                      136K
    Memory tag=243 (reserved)          30.0M        reserved VM address space (unallocated)
    Memory tag=244                      320K
    STACK GUARD                        56.1M
    Stack                              16.1M
    VM_ALLOCATE                           8K
    __DATA                             12.1M
    __IMAGE                             528K
    __LINKEDIT                         53.7M
    __TEXT                             93.8M
    __UNICODE                           544K
    mapped file                        18.6M
    shared memory                       308K
    ===========                      =======
    TOTAL                             410.1M
    TOTAL, minus reserved VM space    380.1M

  • Time Machine backs up everything all the time

    Time Machine is backing up every file all the time. This is a recent development.
    Don't know if this is related but I installed 10.6 on an external HD recently. I was told there wasn't room on the time machine disk so i turned off time machine. I used that boot disk for a week and then switched back to the 10.5.8 drive. After that but I can't be sure the exact date is correlated I noticed the Time Machine backup.

    trinko wrote:
    I figured out how much is being backed up by looking at the size of the files on the time machine disk in the finder and with omnidisksweeper.
    Those won't show an accurate picture. Time Machine uses an unusual and complex structure, involving multiple hard links (sort of like aliases) at both the file and folder level. The files that were the same at the time of each backup will be counted +*in each backup,+* although they were only backed-up once; the total will exceed the total amount of space used on the disk.
    For some reason on Mar 6 Time machine did a new full backup--650GB. Then it said it couldn't do any incremental backups because there wasn't enough free space--the drive had about 300GB free but Time Machine said it needed another 302GB which makes me think it wanted to do another full backup.
    Yes, that's possible. Some of the common causes are listed in #D3 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
    When TM decided it needed to do a full backup, it likely deleted all but the last one, trying to make enough room. Unfortunately, your logs for March 6 are probably gone by now, so we can't figure out exactly what happened then, much less why.
    I then excluded all but 100G of files. Time machine did a full backup of that 100G and then on the next days backup it also did a full backup. Files that hadn't been touched were copied based on looking in the Finder and omnidisksweeper said the files were taking the full amount of space as well.
    Again, that's not necessarily so. Click here to download the TimeTracker app. It shows most of the files saved by TM for each backup (excluding some hidden/system files, etc.). Some prefer the BackupLoupe application.
    Either one should clarify whether everything is really being backed-up each time. Take a look at the subsequent backups from after you excluded all but 100 GB, and post back with your findings.

  • Time machine keeps trying to backup

    I recently installed Yosemite on my Macbook Pro. I have Time Machine set to off, because it keeps trying to do backups, even though it's turned off.
    I removed Time Machine Editor because I kept getting a conflict notification. But now I keep getting notifications that say, "Time Machine couldn't back up to Seagate Backup Plus Drive".
    Is this a Yosemite problem? I haven't had this happen before.

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
    Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
    CLEAR THE WORD "Starting" FROM THE TEXT FIELD
    so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    ☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
    ☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    ☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

  • WAKE UP APPLE. SpotLight & Time-Machine effectively non-functioning after 10.7.5 combo update

    I have just done a complete clean restore from Snow Leopard DVD, doing all its Updates. Then, installed Lion from App store and did the 10.7.5 Combo update. (All that took 2 days).
    Time-Machine and Spotlight non functioning....
    Turned off Spotlight and Time-Machine got my apps & data back...
    Turned off Time-Machine and turned on Spotlight - nothing.
    Followed every combination of the many many helpful tips in this discussion group (involving Onyx, Terminal, Console, Privacy, removing all external drives etc etc). Finally Spotlght began to index.....
    3 days later, it was about 60% complete but slowing down. I rebooted (nothing else) and now Spotlight has restarted the Index once again and I have 3 weeks to wait now.... (Ihave about 600 Gbyte of data on a 1 Tbyte disk)
    Many others have had similar problems
    So clearly there is a significant bug in the system - with no sure fire workaround - and no apparent reaction from Apple staff about what they are doing or what sequence of actions one needs to take to resolve this issue.
    This is sad - Apple is going the same way as IBM, DEC, Microsoft, Adobe - loading functioning systems with more and more bells and whistles until finally they trip over their own feet with the complexity of the whole works.
    I feel entitled to moan - having owned nothing but Apple computers for 30 years.
    (I tried to upgrade to Mountain Lion two weeks ago, but the App store installation just froze and Apple say the DVD drive is a dying species and will supply no disks or other media to do proper restores.....!)
    ANY IDEAS ABOUT HOW TO WAKE APPLE PEOPLE UP!

    Time Machine just doesn't seem to function with lion or Mountaain Lion. I don't know about Spotlight, but I use Intego Backup Assistant for my backup and its doing fine.

  • HT201250 Will Time Machine Back Up Everything On My Mac?

    I have to submit my Macbook Pro into the store to get the USB Port fixed and they recommended backing up my computer before submitting it. I found Time Machine on here and started to back up on it... I just wanted to make sure everything will be backed up (i.e. iPhoto pictures, music on iTunes...etc)

    It should.
    I'd make 2 backups on 2 different drives - oops happen. It can be either 2 Time Machine or Time Machine and a clone.
    Clone  - Carbon Copy Cloner          (Often recommended as it has more features than some others)
    Clone – Data Backup
    Clone – Deja Vu
    Clone  - SuperDuper
    Clone - Synk
    Clone Software – 6 Applications Tested
    Commonly Used Backup Methods

  • Time Machine Fails trying to create a backup folder on Lion

    I just got a new 27 In 3.1 Ghz iMac. I've got 16gig of RAM. I purchased a new USB portable drive to use for Time Machine Backups. The system drive is 1TB with about 250 gig free (I moved a bunch of stuff from my old iMac with the Migration Assistant). The USB drive is also 1TB.
    It looks like Time Machine has copied over most of the data, but I keep seeing the message after a backup is complete. I tried erasing the drive and zeroing it out and then repartitioned as Mac Journaled. and when I started a new full Time Machine backup it failed with the same results. I'm pretty sure there is no issue with this drive especially after doing an erase writing all zeros to it...I'd have expected a failure there if the drive had some type of defect with writes.
    Anyway, does anyone have any suggestions? I'd like to get this thing going and working without errors to know that my data is safely backed up.

    Arghhhhhhhhhhhhhhhhhhh!!!!!!
    After waiting since October for a fix, I have now upgraded the firmware on the Time Capsule and installed the new Airport Utility, released yesterday, and the situation is even worse.
    Up until now, the Airport Utility had an option to disconnect all drives manually and the Time Capsule would then work until the next reboot – a temporary (?) work-around.
    Now that option does not exist in the new-look Airport Utility. And the Airport Utility installation can’t be rolled back and the old utility won’t restore.
    The sparesbundle is still not accessible. Anyone worked out a work-around in the new environment yet?
    I have another Time Machine backup working fine to a trusty old Lacie Drive so erased the one on my Time Capsule to see if that works. I have renamed the Capsule and the Time Capsule Drive.  But to build another full backup will take at least two days and I shall be away from tomorrow and am reluctant to leave the Capsule and computer up and running for a week. And I’ll bet the sparsbundle will still be nowhere to be found.
    How can Apple screw up so badly when they are to become the richest company in the entire world and – soon – will have more cash in the bank than the entire United States? Can’t they afford someone who really can sort this out? Especially when a Firewire connected hard drive – my trusty and simple LaCie – works fine.
    Words, almost, fail me.

  • Time Machine backing up everything EXCEPT my Desktop

    Well i used Time Machine to back up my LaCie 500GB Firewire HD. Never a hassle before, but i'm wondering if there is a glitch possibly with 10.5.7 that isn't allowing it to backup my Desktop.
    I went into the Time Machine preferences, into the Options, and there is nothing listed in the "Do Not Backup" pane - except for the External drive itself. I did not physically tell it to exclude anything, and there is nothing else there.
    So it appears that everything is being backed up normally, except when i enter Time Machine, there is no Desktop folder, just all the other folders/files, etc. Even going "Back In Time" i was unable to locate a backed up Desktop folder.
    So i messed up anyways and did a clean install on my MacBook Pro (knowing that i could use Migration Assistant to get my machine back up and running again). And when i did this, it restored everything except what was on my Desktop.
    So now i'm back up and running again with a perfectly normal computer (except what should be on my Desktop now), and i selected my Time Machine backup disk again, and made double sure there was nothing in the "Exclude" window pane - but there is still no desktop folder again after i did a complete backup all over again.
    Does anybody have any ideas, or know if there is possibly a glitch with maybe 10.5.7 or something that is not allowing it to backup my Desktop? Thanks!
    Jason

    That is truly odd. Not really sure why this would occur, but for a start do this:
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger, and 4.1 for Leopard) and/or TechTool Pro (4.6.1 for Leopard) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    Does this fix the problem after you force another TM backup?

Maybe you are looking for

  • Shocked by lack of features on Mac version compared to Windows. Why?

    Just downloaded Premiere elements 11 and shocked to find that the full set of features are not supported on the mac version, most notably the chroma, green and blue keying effects/ filters. Why is this?? I use a mac not as a fashion statement, but be

  • Connectivity - airport/Itunes

    My itunes connectivity (to to airport express and to my stereo) worked flawlessly when i had the base station set up as a separate network. The down side was I couldn't be online at the same time. Now that I figured out how to set up under the same n

  • Highlighting nodes in a JTree

    Hi, I'd like to know how I can produce the efect of highlighting nodes in a JTree when the mouse moves over the JTree. Thanks

  • APEX 4 Multiple Validation on one Item - Stop after single Failure

    Hi I'm trying out the fantastic new features of APEX 4 - Well done to the APEX team!! Using page item validation, I've applied three validations ('cos that's how I think it works) to a page item. 1. Check if the value entered is numeric 2. Check if t

  • Performance with unspecific where clause

    Hi gurus, at the moment I do have a sql statement on a view with an unspecific where clause like select from <view> where <textfield> like %whatIsearch% The text field is not in the key fields which are used to create the view. An index on <textfield