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

Jun 21, 2010 11:49 AM in response to nxnw

The last time I lost AFP, I noticed that I did not, in fact lose everything.

I lost two volumes (the ones everyone uses every day), but did not lose network home directories (which are only set up for certain occasional users).

There are three differences between the home directories and the two volumes that were dropped:
1. The sharepoint of each dropped volume was its root directory, i.e. /Volumes/ Sharepoint /. The home directories were at Volumes/ RootDirectory / Sharepoint / UserDirectory /
2. The home directories were automount enabled;
3. The dropped volumes were on an internal drive. The home directories were on an external.

I am not sure if any of the above is a key to figuring this out, but I do think it is significant that AFP is actually still running.

Jul 7, 2010 11:42 PM in response to Nick Collingridge

We've been having the same issues, and have just started to use Time Machine Editor (http://timesoftware.free.fr/timemachineeditor/) to force TM to backup after everyone has left the office (we never really needed to keep hourly backups, so it isn't an issue for us) - not perfect for all, but is a good workaround for us. So far we haven't had any AFP drop outs at all (touch wood!).

Jul 9, 2010 8:04 AM in response to Nick Collingridge

We called Apple Support and they have quickly identified this problem and suggested this solution which has been working for us: On the server, in System Preferences (not Server Prefs) bring up TimeMachine and click Options click + to add an exclusion, click Show Invisible Items and select /private.

Since this change our network share are not unmounted anymore while TimeMachine backups are running.

Oct 12, 2010 2:37 PM in response to Philipp Reinheimer

(X.6.4 Server)

We are not using the server for Time Machine, but our logs are similar to yours. Specifically, "Got Error calling WriteLock on lock" at the time of AFP crash:

Oct 12 11:56:59 mm /usr/sbin/AppleFileServer[128]: Got Error calling WriteLock on lock < 0x164 > error < 0 >
Oct 12 11:57:01 mm com.apple.ReportCrash.Root[58863]: 2010-10-12 11:57:01.895 ReportCrash[58863:2703] Saved crash report for AppleFileServer[128] version ??? (???) to /Library/Logs/DiagnosticReports/AppleFileServer 2010-10-12-115701localhost.crash
Oct 12 11:57:02 mm com.apple.launchd[1] (com.apple.AppleFileServer[128]): Job appears to have crashed: Segmentation fault

Any luck on finding a cure?

Dec 13, 2010 10:55 AM in response to Nick Collingridge

We've had this problem intermittently on two systems going back to at least 10.6.3, and have never been able to isolate the issue. Always seems slightly different each time.

However, the 10.6.5 update seems to of finally fixed it, but going to wait just a bit longer before we use on our production file server. Anyone else had good results with this update?

Simon.

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.