Odd Intermittent Time Machine error - volume in use

Occasionally when backing up to a shared time machine volume from a system running 10.7 server it gives an error message that the volume is in use. /Backups adds a number next to itself such as /Backups-1 or /Backups-15. The backups seem to automatically occur the next hour or so, however on occasion it will pop up the error throughout the day.
Specifics about my system:
10.7 MBAir 11" 2010 1.6GHz C2Duo -- Filevault2 encryption turned on, fresh time machine backup started after the filevault was enabled.
Shared volume:
iMac running 10.7 server, sharing a Drobo as a Time Machine backup location.
All other systems on the network seem to backup fine to it however no others are operating with filevault enabled. Also none of the other systems are named the same Computer Name, and each computer's backup appears as a separate sparseimage on the shared backup volume.
Anyhow, it looks and sounds like a bug, but just wondering if anyone else was seeing the same issue. I was unable to find anything on the internet or the discussion boards about this issue.

Of course as soon as I post this I finally find the troubleshooting procedures in the FAQ... That seems to have worked.

Similar Messages

Intermittent Time Machine Error -1

I have a late 2008 MacBook Pro 2.8 GHz with 4 GB of RAM running Mac OS X 10.7.3. I have Time Machine backups performed through a Mac Mini running Mac OS X 10.7.3 Lion Server (clean install) to an external drive attached to the mini via Firewire 800. I have three machines backing up to the server and prior to Lion, had no issues. Since the migration to Lion, only one machine, the one listed above intermittently fails to backup with the error -1, unable to mount volume. I have downloaded all of the latest patches for all clients and the server. I tried installing the "Turbo" device driver from Western Digital for the drive since no other device drivers are available (WD site says they are provided by the OS). This made no difference and the other machines continue to backup without a problem. The client having issues will backup for as much as a day or two, then throw the error again. In addition to the above I have tried the following:
Run disk utilties to verify no disk errors - no issues found
I did a manual backup to another disk, reformatted the Time Machine Disk backed up all machines - same problem
WD Smartware updated to 1.3.3.8 - latest version released after Lion and states Lion compatible.
Verified through Workgroup Manager that MAC addresses and hardware UUID are correct for all machines (Software Update through the Server works fine).
Tried backup up connected by ethernet versus WiFi - problem still intermittent and is independent of network connection type.
What next? Anyone else seeing this?

See #C17 in Time Machine - Troubleshooting.

Intermittent Time Machine Error

I am wondering if anyone else ha experienced this. I have Time Machine backing everything up on my Mac to a hard drive, but I keep on getting an error message. It says that "the back up volume is read only" and prompts me to change it....when I eject the drive, unplug it, and then plug it in again, it appears in the disks window of the Time Machine preferences, and I select it and its fine for about 24-hours. Then the same fault occurs when TM attempts to back up. It happened once before, but eventually stopped....any suggestions? It is driving me crazy as I have to go through the same procedure every day now.......Thanks!

Hi Barry,
Definitely not in there....in fact there is no time machine preferences document at all! I meant to add in my initial blurb that my husband has exactly the same Mac, operating system and back up disk for Time Machine and he doesn't get any problems.
Anything else you can suggest?
Thanks so much.....JO

Idea: Time Machine errors could be used for telling people everything is OK

In the event of catastrophic good luck, abort.
Just a little levity for all those struggling with Time Machine.
Also, for those having "not enough space" errors on the initial backup, I found that if I excluded the two largest directories and let Time Machine do its thing, it didn't complain when those were taken off the exclusion list on subsequent backups.

Ok, this is getting ridiculous. Anyone else seeing this sort of behavior?
Message was edited by: irowboat

I have not been able to back up for2 days. Time machine error message: /Volumes/Data/David's MacBook Air.sparsebundle" is already in use.

I have not been able to back up for2 days. Time machine error message: /Volumes/Data/David’s MacBook Air.sparsebundle” is already in use.
What now?
Macbook Air.
Was working fine for the past year until now.

See more like this on the right.. this is the most common error reported here since mountain lion came out..
Or read C12.. http://pondini.org/TM/Troubleshooting.html
Or just restart the whole network.. in right order from off.. modem.. router / TC.. clients 2min gap.

HT3275 Time Machine Error: The backup disk image "Volumes/Data/My Macbook Pro.sparsebundle" is already in use. (How do I correct this issue?)

Time Machine did not back up:
Time Machine Error; ("The backup disk image "/Volumes/Data/My MacBook Pro.sparsebundle" is already in use.")
How do I correct this issue?
Thanks!

You need to be careful Bob.. people might take this literally.
Bob Timmons wrote:
How do I correct this issue?
Call the exterminator to get rid of the bugs in Lion and Mountain Lion.
https://discussions.apple.com/thread/5222487?tstart=0

Time Machine error: The backup disk image "/Volumes/----/----MacBook Pro.sparsebundle" is already in use and resource unavailable?

I have a MacBook Pro 13" 2010 model running Mountain Lion. I have always been able to use Time Machine with my Time Capsule. Just today I have been receiving the same error message whenever I would back up my computer:
I removed my name before "MacBook Pro". It takes a long time "Looking for backup disk..." first. The disk I put with the time capsule is called Huge Backup, and in Huge Backup there is my sparsebundle file called "----- MacBook Pro." When I open Finder, open my time capsule, and then open my sparse folder, it should mount a drive where I can see my computer's backups. That doesn't work. Then I get this message:
I once again removed my name before "MacBook Pro" but I can open my sister's sparsebundle who is running Mountain Lion on the same network and her backups work fine. I have researched this topic and have tried to repair the disk in Disk Utility, remount all the drives, remove the drive and restart the backups, and even restart my computer and the Time Capsule. Nothing worked. It just was working yesterday, but now I get this in the settings along with a caution symbol in my menubar:
Is there anything I could do to fix this? Reconnecting it in AirPort Utility (5 or 6) didn't work. Also, for some reason, the error renamed Huge Backup to Huge Backup-1 as you can see above and below in the messages. I downloaded the Time Machine Buddy widget and this is the error report I got. I replaced my names or private info with [-----]. By the way, the network is called NDR Network, and the Time Capsule is alled NDR Time Capsule. Here's the error I keep getting:
Starting manual backup
Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
Disk image already attached: /Volumes/Huge Backup/[-----]'s MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a483e6c0 {MessageParameters=(
Ejected Time Machine network volume.
Waiting 60 seconds and trying again.
Attempting to mount network destination URL: afp://[-----];AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backu p
Mounted network destination at mount point: /Volumes/Huge Backup using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
Disk image already attached: /Volumes/Huge Backup/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a343d430 {MessageParameters=(
Ejected Time Machine network volume.
Waiting 60 seconds and trying again.
Attempting to mount network destination URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
Mounted network destination at mount point: /Volumes/Huge Backup-1 using URL: afp://Rohan;AUTH=SRP@NDR%20Time%20Capsule._afpovertcp._tcp.local/Huge%20Backup
Disk image already attached: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7ff0a34410c0 {MessageParameters=(
Ejected Time Machine network volume.
Giving up after 3 retries.
Backup failed with error: 31
[SnapshotUtilities mountPointForVolumeRef] FSGetVolumeInfo returned: -35
Failed to eject volume (null) (FSVolumeRefNum: 0; status: -35; dissenting pid: -1)
Failed to eject Time Machine disk image: /Volumes/Huge Backup-1/Rohan's MacBook Pro.sparsebundle
Please help!

I didn't remove all of my names, so just ignore that...

I am running 10.7.5 and getting Time Machine error The backup disk image "/Volumes/Data/Kathy P's MacBook.sparsebundle" is already in use. what do i do now?

i am running 10.7.5 on an older MacBook and getting Time Machine error The backup disk image “/Volumes/Data/Kathy P’s MacBook.sparsebundle” is already in use. what do i do now?

See Pondini's TM FAQs, for starters.

TS1550 My time capsule will not back up. There is a time machine error message that states "The backup disk image "/volumes/Backup/Jane's MacBook Pro.sparsebundle" is already in use. How do I correct this problem?

My time machine will not back up. I get a Time Machine Error message that reads: "The backup disk image "/Volumes/Backup/(myname)'sMacBook Pro.sparsebundle" is already in use.
I have not been able to back up for two weeks, I think this occurred after an update to the operating system, but I am unsure.
How do I correct this problem?

Have you tried restarting the computer? Also, see Time Machine Error from this pages sidebar under More Like This.

HT3275 Time machine error, backup disk image "/volumes/data-1/.sparesbundle " already in use. I don;t know what this means, can someone help?

My Mac mini time capsule is showing an error Time machine error, backup disk image "/volumes/data-1/.sparesbundle " already in use. I don;t know what this means, can someone help?

I had a similar problem and I solved it as follows -
In Time Machine - > I deselected time capsule Data Disk as a destination.
Then I pulled the power plug on the Time Capsule, twiddled my thumbs for 15 secs, plugged the power back in.
Went back t Time Machine -> Re-Added the Time Capsule Data Disk as destination. And then tested by selecting Backup Now.
All went well and the backup picked up from before the problem.
BTW - I also have a USB drive connected to Time Capsule that is an alternate disk for Time Machine to backup.
In Mountain Lion the GUI lets you add more than one Time Machine backup destinations very easily so I think it a good idea to have redundancy.
Hope this helps.

"No such file or directory" errors on Time Machine backup volume

I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I "cd" into some folders (but not all) and do a "ls -la" command, I get a lot of "No such file or directory" errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do "ls -a" everything appears normal on both systems (no error messages anyway).
It appears to be the case that the folders that have the problem are folders that Time Machine has created as "hard links" to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.
I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK - so basically by switching the volume the problem switches also on who shows the "no such file or directory" errors.
Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these "hard links" to folders.
There is utility program written by Amit Singh, the fella who wrote the "Mac OS X Internals" book, called hfsdebug (you can get it from his website if you want - just do a web search for "Mac OS X Internals hfsdebug" if you want to find it ). If you use it to get a little bit more info on what's going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:
mac1:xxx me$ pwd
/Volumes/MyBackups/yyy/xxx
mac1:xxx me$ ls -a
. .DS_Store D2
.. Documents D3
mac1:xxx me$ ls -lai
total 48
280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 .
282780 drwxr-xr-x 12 me staff 442 Jan 17 14:03 ..
286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 Documents
729750 drwx------ 104 me staff 7378 Jan 15 14:17 D2
728506 drwx------ 19 me staff 850 Jan 14 09:19 D3
mac1:xxx me$ hfsdebug Documents/ | head
<Catalog B-Tree node = 12589 (sector 0x18837)>
path = MyBackups:/yyy/xxx/Documents
# Catalog File Record
type = file (alias, directory hard link)
indirect folder = MyBackups:/.HFS+ Private Directory Data%000d/dir_135
file ID = 728505
flags = 0000000000100010
. File has a thread record in the catalog.
. File has hardlink chain.
reserved1 = 0 (first link ID)
mac1:xxx me$ cd Documents
mac1:xxx me$ ls -a | head
.DS_Store
.localized
.parallels-vm-directory
.promptCache
ACPI
ActivityMonitor2010-12-1710p32.txt
ActivityMonitor2010-12-179pxx.txt
mac1:Documents me$ ls -lai | head
total 17720
135 drwxrwxrwx 91 me staff 3944 Jan 7 02:53 .
280678 drwxr-xr-x 5 me staff 204 Jan 20 01:23 ..
144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
146 drwxr-xr-x 2 me staff 68 Feb 17 2009 .parallels-vm-directory
147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
148 drwxr-xr-x 2 me staff 136 Aug 28 2009 ACPI
151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
So you can see from the first few lines of the "ls -a" command, it shows some file/folders but you can't tell which yet. The next "ls -la" command shows which names are files and folders - that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the "hfsdebug" info shows some details of what is really happening in the "Documents" folder, but more about that in a bit.
And here are what a "ls -a" and "ls -al" look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:
mac2:xxx me$ pwd
/Volumes/MyBackups/yyy/xxx
mac2:xxx me$ ls -a
. .DS_Store D2
.. Documents D3
mac2:xxx me$ ls -lai
total 56
280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 .
282780 drwxr-xr-x 13 me staff 398 Jan 17 14:03 ..
286678 -rw-r--r--@ 1 me staff 21508 Jan 19 10:43 .DS_Store
728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 Documents
729750 drwx------ 217 me staff 7334 Jan 15 14:17 D2
728506 drwx------ 25 me staff 806 Jan 14 09:19 D3
mac2:xxx me$ cd Documents
mac2:Documents me$ ls -a | head
.DS_Store
.localized
.parallels-vm-directory
.promptCache
ACPI
ActivityMonitor2010-12-1710p32.txt
ActivityMonitor2010-12-179pxx.txt
mac2:Documents me$ ls -lai | head
ls: .parallels-vm-directory: No such file or directory
ls: ACPI: No such file or directory
... many more "ls: ddd: No such file or directory" error messages appear - there is a one-to-one
correspondence between the "ddd" folders and the "no such file or directory" error messages
total 17912
728505 drwxrwxrwx 116 me staff 3900 Jan 7 02:53 .
280678 drwxr-xr-x 6 me staff 264 Jan 20 01:23 ..
144 -rw-------@ 1 me staff 39940 Jan 15 14:27 .DS_Store
145 -rw-r--r-- 1 me staff 0 Oct 20 2008 .localized
147 -rwxr-xr-x 1 me staff 8 Mar 20 2010 .promptCache
151 -rw-r--r-- 1 me staff 6893 Dec 17 10:36 A.txt
152 -rw-r--r--@ 1 me staff 7717 Dec 17 10:54 A9.txt
If you look very close a hint as to what is going on is obvious - the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it's 728505 in the remote mounted case for mac2. So it appears that these "hard links" to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the "hfsdebug" shows even better as you can clearly see the REAL location of the Documents folder is in something called "/.HFS+ Private Directory Data%000d/dir_135" that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the "cd Documents" I don't go into the inode 135, but into the inode 728505 (look close at the "." entry for the "ls -la" commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.
Anyone have any ideas how to fix this so that "ls -l" commands don't generate these "no such file or folder" messages?
I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call - do a "man 2 link" if you are curious how it works.
I'm well aware of the issues and the conditions when they can and can't be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.
Do not try these hard links to folders on your own without knowing what they're for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don't say I didn't warn you first.
Thanks ...
-Bob

The problem is Mac to Mac - the volume that I'm having the issue with is not related in any way to Time Machine or to TimeCapsule. The reference to TIme Machine is just to illustrate the problem exists outside of my own personal work with hard links to folders on HFS Extended volumes (case-sensitive in this particular case in case that matters).
I'm not too excited about the idea of snooping AFP protocol to discover anything that might be learned there.
The most significant clue that I've seen so far has to do with the inode numbers for the two folders shown in the Terminal window snippets in the original post. The local mounted case uses the inode=728505 of the problematic folder which is in turn linked to the hidden original inode of 135 via the super-secret /.HFS+... folder that you can't see unless using something like the "hfsdebug" program I mentioned.
The remote mounted case uses the inode=728505 but does not make the additional jump to the inode=135 which is where lower level folders appear to be physically stored.
Hence the behavior that is seen - the local mounted case is happy and shows what would be expected and the remote mounted case shows only files contained in the problem folder but not lower-level folders or their contents.
From my little knowledge of how these inode entries really work, I think that they are some sort of linked list chain of values, so that you have to follow the entire chain to get at what you're looking for. If the chain is broken somewhere along the line or not followed correctly, things like this can happen. I think this is a case of things not being followed correctly, as if it were a broken chain problem then the local mounted case would have problems also.
But the information for this link in the chain is there (from 728505 to the magic-135) but for some reason AFP doesn't make this extra jump.
Yesterday I heard back from Apple tech support and they have confirmed this problem and say that it is a "implementation limitation" with the AFP client. I think it's a bug, but that will have to be up to Apple to decide now that it's been reported. I just finished reporting this as a bug via the Apple Bug Reporter web site -- it's bug id 8926401 if you want to keep track it.
Thanks for the insights...
-Bob

HT3275 Time Machine error. Unable to complete backup. An error occurred while copying files to the backup volume. Tried restarting, remounting external WD drive. Still cannot backup.

Time Machine quit backing up files. Bought a new WD external drive. Worked for awhile, then quit backing up. Tried restarting computer, remounting drive. Message: Time Machine Error. Unable to complete backup. An error occurred when copying files. Suggestions?

Thanks so very much for your help!! I'm boggled by it and now just about ready to dump the whole idea of Time Machine and backup using a cloning program. Maybe TM is only guaranteed to work well with Time Capsule these days?
Today there again was no backup. I did as you suggested, looked into Console. It showed many lines of "(Error) DiskStore: No block in wakeup" and also repeatedly "(Warning) DiskStore: Ignored bogus fetch...".
So I created a marker and attempted to initiate a backup, keeping Console open and refreshed. Here's what I got:
8/19/13 5:18:40.385 PM Console: Marker - Aug 19, 2013 5:18:40 PM
8/19/13 5:19:48.844 PM com.apple.backupd: Starting standard backup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.484 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.494 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.502 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.506 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Error) DiskStore: No block in wakeup
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.507 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:37ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.508 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:38ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.510 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:40ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:00.511 PM mds: (Warning) DiskStore: Ignored bogus fetch for <MDSQueryWithBlockTask: 0x7fd15ce03400>{taskID:0x0000103a age:41ms} (not live not complete) _kMDItemQueryPath=418546
8/19/13 5:20:20.000 PM kernel: USBF:          58091.976          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:20:51.000 PM kernel: USBF:          58122.985          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:22.000 PM kernel: USBF:          58153.992          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:21:53.000 PM kernel: USBF:          58185. 2          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:24.000 PM kernel: USBF:          58216. 14          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:22:55.000 PM kernel: USBF:          58247. 25          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:26.000 PM kernel: USBF:          58278. 41          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:23:57.000 PM kernel: USBF:          58309. 51          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:28.000 PM kernel: USBF:          58340. 59          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:24:59.000 PM kernel: USBF:          58371. 68          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:25:30.275 PM xpchelper: for uid: 501 -- timeout while waiting on FSEvents flush; clearing cache.
8/19/13 5:25:30.000 PM kernel: USBF:          58402. 82          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:01.000 PM kernel: USBF:          58433. 96          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:26:32.027 PM com.apple.backupd: Backing up to: /Volumes/TMBackups/Backups.backupdb
8/19/13 5:26:32.000 PM kernel: USBF:          58464.112          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:02.653 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:02.657 PM com.apple.backupd: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TMBackups/Backups.backupdb/David‚Äôs iMac size:37
8/19/13 5:27:03.000 PM kernel: USBF:          58495.121          AppleUSBEHCI[0xffffff800a927000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 7, EP: 1)
8/19/13 5:27:12.668 PM com.apple.backupd: Backup failed with error: 2
During this 9-minute timeframe Finder also was inoperative - according to Activity Monitor: "Not Responding".
I'm thinking it's the standalone Buffalo backup drive not waking up, and so everything comes to a screeching halt. Do you also think I should abandon TM and just do manual backups every day using a clone program?

Time Machine Error -- Backup Volume is Read Only

I suddenly started getting this error today when Time Machine runs. I use a 1 TB WD My Book as my Time Machine drive. When I select get info on the backup folder on the WD drive and check sharing and Permissions tab, it states directly under this label that "you can only "read" even though I am the administrator and it shows me as having read and write access in the table below the "you can only read" message.
Any thoughts?

See the following:
What to do if Time Machine reports you don't have permission
This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.
The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.
[Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:
sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx
The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.
You'll have to enter your admin password (which you won't see) which is normal.
This was edited by Kappy just for cleanup.
Enable Finder to Show Invisible Files and Folders
Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.
defaults write com.apple.finder AppleShowAllFiles TRUE
To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.
defaults write com.apple.finder AppleShowAllFiles FALSE
Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.

"Time Machine Error The backup volume is read only"

Lately, every time I try to backup to my Time Capsule using Time Machine it fails and I get a message saying "Time Machine Error The backup volume is read only. To select a different volume, open system preferences and choose Time Machine" So I do that and I see the Time capsule listed. I don't want to select anything but the Time Capsule, cuz what else do I have, right? Am I wrong in assuming the "backup volume" is the Time Capsule? Anyway, I have tried changing the permissions on the time capsule, but when I get the "get info" box for the time capsule, there is not an option to change those settings, they are grayed out. Every thing worked well for about a week and then this started. My backup volume must have been "Read & Write" at first, because I can see what was backed up when I open Time Machine. Anybody have a clue what's going on? How can I make the back up volume "Read & Write" again and why did it change to "Read Only?"

Nope, I am using the same passwords as ever, both users have the same password, BTW. The password I gave to the Time Capsule is different, tho, but that password is for the wireless aspect of the Time Capsule, so that wouldn't have anything to do with it, would it?
I also get a message box that says "Disk Repair The disk "Backup of XXX's Computer" was not repairable by this computer, it is being made available to you with limited functionality. You must back up your data and reformat the disk as soon as possible." This box appears in conjunction with the appearance of the Norton's virus scan box scanning the time capsule.

Time Machine Error...sparsebundle in use

New Time Capsule; overnight backup successful; there's a disc image which when massaged appropirately generates a list of files that looks like my hard disc, who is named 'FMBP', probably standing for F's MacBookPro. So far, so good.
However, every hour it tells me "Time-Machine Error: The backup disk image “/Volumes/Data-1/FMBP.sparsebundle” is already in use." My impressions is that it is in use containing the files that it just backed up.
Speaking softly to, or kicking, the Time Capsule, does not help. Fumbling about clicking things labelled "Time ..." sometimes does something unexpected--after while--but does not generate a backup.
The instructions say to keep books 'n stuff off of the Time Capsule, lest they impede cooling. The cat points out that he is *not* a book, and if I'm not going to heat the house during this European cold spell, he should be allowed to sit on it. But surely OS X doesn't consider this 'using' the sparsebundle?
Anyone know how to 'unuse' sparsebundle?

Power down both your computer and the Time Capsule. Start both up again and try a backup.
Or, if you do not want to power down both devices and restart, you can open AirPort Utility and click Manual Setup. Click the Disks icon, then click the Disks tab just below the icons. then click Disconnect All Users.
Then try another backup.

Odd Intermittent Time Machine error - volume in use

Similar Messages

Maybe you are looking for