You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

10.6.3 - Apparent spontaneous unmount of network volumes

Since updating my server to 10.6.3 I am experiencing spontaneous unmounts of AFP volumes from clients running both 10.6.2 and 10.6.3. In both cases the Console on the client systems reports the following messages:

02/04/2010 3:07:53 am kernel AFP_VFS afpfsCacheLookup: got 2 on root vnode, unmounting vol
02/04/2010 3:07:53 am kernel AFP_VFS afpfs_unmount: /Volumes/XXX, flags 524288, pid 626

(Obviously the PID on the second system is different.)

In both cases there was a Time Machine backup happening during this occurrence which commenced prior to the unmount, but there had been many previous backups which did not trigger an unmount so I am unsure whether this is significant or not.

The only other clue is that on the 10.6.3 client (but not the 10.6.2 client) the following two lines appear in the console immediately prior to the unmount event:

02/04/2010 3:07:53 am KernelEventAgent[40] tid 00000000 type 'afpfs', mounted on '/Volumes/XXX', from 'afp_000000004oMw0oYHtK3gzaWf-2.2e000004', dead
02/04/2010 3:07:53 am com.apple.KernelEventAgent[40] KernelEventAgent: sysctl unmount(afp000000004oMw0oYHtK3gzaWf-2.2e000004): Resource busy

This is definitely becoming an issue for me which I desperately need to resolve.

One other symptom I am experiencing is that both clients seem to repeatedly "lose" their mail POP3 passwords and these need to be re-entered to retrieve mail. I suspect what's actually happening is that authentication is incorrectly failing on the server, triggering the request to re-enter the password, and I wonder whether this is a factor in the AFP unmounts. What's significant here is that this is happening on both the 10.6.2 and 10.6.3 clients; the only common factor is that the server has been updated to 10.6.3.

Mac OS X (10.4)

Posted on Apr 2, 2010 4:14 AM

Reply
41 replies

May 27, 2010 4:55 AM in response to zirinisp

Question for the crowd:

1- How many of you are backing up to a drive that is directly connected using Time Machine?

2- How many of you are backing up to a network drive with Time Machine, not including a Time Capsule or Airport Express?

3- How many of you are backing up to a Time Capsule?

4- How many of you are backing up to an Airport Express-shared disk?

(All using Time Machine, of course.)

I noticed that the problems didn't occur until after 10.6.3, but maybe also Time Capsule Update, and I didn't have problems with a direct-connected drive (other than the drive kept crapping out, but I think that is unrelated). Problems showed up when I moved to an Airport Express shared disk, and only after mucking about with the password to get it to mount. I.e., maybe it has somethig to do with the need to authenticate to the served volume which crashes DirectorySomethingOrOther, which happens simultaneously when the problem occurs.

May 27, 2010 10:12 AM in response to mcptron

mcptron wrote:
i'm using a directly connected firewire 800 drive for tm backups on a mac mini


Same here. I have TM running only once a day, at 5 am, and this is when the failure has occurred on each occasion.

Also, it has not happened for a while. May 5, May 10, but not since (it's now the 27th). The only subsequent change I have made is the Java upgrade, and even that was just a couple of days ago.

May 27, 2010 6:40 PM in response to Bill Eccles

SLS 10.6.3 MacPro, TM drive is in a drive bay.
After many tests, every AFP issue has been when TM "disconnects"... even though the TM drive is internal and never dismounts. The bug looks to be that TM is also disconnecting AFP share points when TM closes out.
The only times AFP share points have gone missing have been at the same moment TM completes a run. But this does not happen at the end of every TM run... still looking for what is different about specific TM runs.

I suggest only manually running TM until fixed, this way you can check AFP when TM finishes. I'm filing a bug, you should too.

Jun 1, 2010 8:30 AM in response to Nick Collingridge

Same here:

10.6.3 Server, OD-Replica with 170 serverbased Userfolders:

Log-File says:

Jun 1 17:03:50 users com.apple.launchd[1] (com.apple.suhelperd[15040]): Exited with exit code: 2
Jun 1 17:04:01 users /usr/sbin/AppleFileServer[13790]: Got Error calling WriteLock on lock < 0x41 > error < 0 >
Jun 1 17:04:01 users com.apple.ReportCrash.Root[15058]: 2010-06-01 17:04:01.936 ReportCrash[15058:2703] Saved crash report for AppleFileServer[13790] version ??? (???) to /Library/Logs/DiagnosticReports/AppleFileServer 2010-06-01-170401localhost.crash
Jun 1 17:04:02 users com.apple.launchd[1] (com.apple.AppleFileServer[13790]): Job appears to have crashed: Segmentation fault


Jun 1 17:20:44 users /usr/sbin/AppleFileServer[15059]: Got Error calling WriteLock on lock < 0x43 > error < 0 >
Jun 1 17:20:46 users com.apple.launchd[1] (com.apple.AppleFileServer[15059]): Job appears to have crashed: Segmentation fault
Jun 1 17:20:46 users com.apple.ReportCrash.Root[16321]: 2010-06-01 17:20:46.881 ReportCrash[16321:2a03] Saved crash report for AppleFileServer[15059] version ??? (???) to /Library/Logs/DiagnosticReports/AppleFileServer 2010-06-01-172046localhost.crash
Jun 1 17:22:21 users /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[15460 ]: No valid tickets, timing out

The situation is critical. Does anyone have the same problems. AFP is crashing daily, sometimes 5-6 times in series...

Jun 9, 2010 5:26 AM in response to Steven Slupsky

This problem keeps recurring and I am hoping against hope that it will be fixed by 10.6.4 as it is proving a total nightmare. Here is another console trail of destruction which shows that the problem is pretty obviously caused when Time Machine attempts to mount the Time Capsule over our network:

09/06/2010 12:46:26 pm com.apple.backupd[8405] Starting standard backup
09/06/2010 12:46:26 pm com.apple.backupd[8405] Attempting to mount network destination using URL: afp://TCURL/OurTimeCapsule
09/06/2010 12:46:26 pm KernelEventAgent[40] tid 00000000 type 'afpfs', mounted on '/Volumes/Vol1', from 'afp_000000004oMw0oYHtK3gzaWf-2.2e00000e', dead
09/06/2010 12:46:27 pm com.apple.KernelEventAgent[40] KernelEventAgent: sysctl unmount(afp000000004oMw0oYHtK3gzaWf-2.2e00000e): Resource busy
09/06/2010 12:46:27 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol
09/06/2010 12:46:27 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol
09/06/2010 12:46:27 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol
09/06/2010 12:46:27 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol
09/06/2010 12:46:27 pm kernel AFP_VFS afpfs_unmount: /Volumes/Vol2, flags 524288, pid 830
09/06/2010 12:46:27 pm kernel AFP_VFS afpfs_unmount: /Volumes/Vol11, flags 524288, pid 830
09/06/2010 12:46:27 pm kernel ASP_TCP CancelOneRequest: cancelling slot 25 error 89 reqID 55436 flags 0x9 afpCmd 0xF0000002 so 0xd92b4c8
09/06/2010 12:46:34 pm com.apple.backupd[8405] Mounted network destination using URL: afp://TCURL/OurTimeCapsule
09/06/2010 12:46:35 pm kernel AFP_VFS afpfs_mount: /Volumes/OurTimeCapsule, pid 8406
09/06/2010 12:46:36 pm hdiejectd[8417] running
09/06/2010 12:46:37 pm com.apple.backupd[8405] QUICKCHECK ONLY; FILESYSTEM CLEAN
09/06/2010 12:46:39 pm com.apple.backupd[8405] Disk image /Volumes/OurTimeCapsule/MySystem.sparsebundle mounted at: /Volumes/Time Machine Backups
09/06/2010 12:46:39 pm com.apple.backupd[8405] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
09/06/2010 12:47:24 pm com.apple.backupd[8405] No pre-backup thinning needed: 1.53 GB requested (including padding), 104.45 GB available
09/06/2010 12:47:34 pm com.apple.launchd[1] (com.apple.netauth.sysagent[8406]) Exited with exit code: 255
09/06/2010 12:48:25 pm mdworker[8388] * Failed to decode data, treating as binary
09/06/2010 12:50:12 pm com.apple.backupd[8405] Copied 5234 files (21.2 MB) from volume Nick iMac HD.
09/06/2010 12:50:26 pm com.apple.backupd[8405] No pre-backup thinning needed: 1.55 GB requested (including padding), 104.45 GB available
09/06/2010 12:51:48 pm com.apple.backupd[8405] Copied 2741 files (36.5 MB) from volume Nick iMac HD.
09/06/2010 12:52:05 pm com.apple.backupd[8405] Starting post-backup thinning
09/06/2010 12:53:20 pm com.apple.backupd[8405] Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/MySystem/2010-06-08-123055: 104.45 GB now available
09/06/2010 12:53:20 pm com.apple.backupd[8405] Post-back up thinning complete: 1 expired backups removed
09/06/2010 12:53:21 pm com.apple.backupd[8405] Backup completed successfully.
09/06/2010 12:53:26 pm com.apple.backupd[8405] Ejected Time Machine disk image.
09/06/2010 12:53:27 pm com.apple.backupd[8405] Ejected Time Machine network volume.
09/06/2010 12:53:27 pm kernel AFP_VFS afpfs_unmount: /Volumes/OurTimeCapsule, flags 0, pid 8497
09/06/2010 12:53:27 pm kernel ASP_TCP CancelOneRequest: cancelling slot 29 error 89 reqID 19148 flags 0x9 afpCmd 0xF0000002 so 0xdda3330
09/06/2010 12:53:36 pm hdiejectd[8417] quitCheck: calling exit(0)

I live in dread of that disconnect dialog popping up, and all the carnage it causes with applications (InDesign CS4 is particularly bad at handling a situation where the network volume disappears on it, although Illustrator CS 4 and Photoshop CS4 seem to have no big problem. Word 2008 is another app that doesn't like it very much although you can normally get through without a force-quit).

Jun 12, 2010 1:57 AM in response to Bill Eccles

I had repeated crashes after upgrading to 10.6.3.

It was crashing every time that there was any concentrated workload on the machine from any program or activity.

After days I discovered that it was spotlight continuing to attempt to index and getting jammed. According to the Activity Monitor it was using 70% of the CPU.

Disabled Spotlight on 1 June 2010 - no crashes since - touch wood.

Check the console and it may be reporting as mds crash or Spotlight Index crash.

If you want to disable Spotlight from 10.6.3 then remove these two files:

com.apple.metadata.mds.plist

com.apple.metadalta.mdwrite.plist

Hope this may help someone.

Cheers,

Syd Chesson

10.6.3 - Apparent spontaneous unmount of network volumes

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.