Benches macOS

15

10.6.3 - Apparent spontaneous unmount of …

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

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.

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    mcptron

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    i have the same problems. in addition, there are random ical server authentication errors.

  2. 0

    mcptron

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    some log info for the ical problems:

    ical accesslog

    127.0.0.1 - - [05/Apr/2010:16:47:20 +0200] "REPORT /principals/
    _uids_/46B346F6-4E55-48D1-B7A0-B4EAD849DC19/ HTTP/1.1" 401 141 "-" "DAVKit/4.0.1 (730); CalendarStore/4.0.1 (976); iCal/4.0.2 (1379); Mac OS X/10.6.3 (10D573)" i=8446 t=8.7 or=1

    ical errorlog

    2010-04-05 16:47:20+0200 [-] [caldav-8011] [PooledMemCacheProtocol,client] [twistedcaldav.extensions#info] Could not find the principal resource for user id: mike

  3. 0

    jonesy16

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm having the same issue after upgrade to 10.6.3. Happens about once a day, always at about the same time of day, and always seems to coincide with TimeMachine beginning its backup routine.

  4. 0

    David Kurtz2

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It's possible that the disk drive has become corrupted. You might want to run Disk Utility and check your drives on your server (and your client machines too, while you're at it.)

  5. 0

    sdwylie

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks David,

    I was having the same problem with both file shares and iCal. From Disk Utility, I ran "Verify Disk Permissions", which came back with a wide range of errors - I then ran "Repair Disk Permissions" and found everything to be working correctly.

    cheers

  6. 0

    mcptron

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    thanks sdwylie,

    i tried your solution and it actually worked for me. the auth problems are gone now after the disk permissions repair.

  7. 0

    uruzone

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problem here in Florida. Sporadic dropping of share points on an Xserve (3 X 1 TB RAID and 48GB RAM), with AFP not even showing those volumes as existing after the upgrade to 10.6.3. Some users are also being asked for their email passwords repeatedly. I restarted AFP to get file sharing working temporarily, and have now repaired disk permissions. I'll report back at the end of the day to say how it worked. We are also running TimeMachine, FWIW.

  8. 0

    Maculous

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I am having the same problem here. It's as if the shares don't exist anymore until restarting AFP. I do have access to my home directory as an admin though, but nothing else. Apple, fix yet?

  9. 0

    roossym

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same problem here.

    After update of SLS to 10.6.3, AFP shares are sporadically not visible until I restart AFP on the server.

  10. 0

    uruzone

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Sorry it took so long to write the follow-up. Permissions repair DID work. Initially.

    However, a few days later, ALL of the share points disappeared completely. No one could see them, and in server admin, they were simply...gone. There were also problems with mail passwords.

    We rebuilt the share points, repaired permissions again and this time I turned off Time Machine. We'll see if it holds up.

  11. 0

    Nick Collingridge

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Latest situation is that the problem is still ocurring regularly. I have tried repairing permissions on the server but this has not changed anything. It is very clear to me that this is some sort of interaction between Time Macine and mounted volumes. Two clients have both just unmounted their network volumes in exactly the same way - the Time Capsule volume has been mounted and then immediately the network volumes are unmounted. Here is a transcript from one of them:

    28/04/2010 2:36:48 pm com.apple.backupd[40394] Starting standard backup

    28/04/2010 2:36:48 pm KernelEventAgent[41] tid 00000000 type 'afpfs', mounted on '/Volumes/Vol1', from 'afp_000000004oMw0oYHtK3gzaWf-2.2e000047', dead

    28/04/2010 2:36:48 pm com.apple.backupd[40394] Attempting to mount network destination using URL: afp://[email protected]/OurTimeCapsule

    28/04/2010 2:36:48 pm com.apple.KernelEventAgent[41] KernelEventAgent: sysctl
    unmount(afp000000004oMw0oYHtK3gzaWf-2.2e000047): Resource busy

    28/04/2010 2:36:49 pm com.apple.backupd[40394] Mounted network destination using URL: afp://[email protected]/OurTimeCapsule

    28/04/2010 2:36:49 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol

    28/04/2010 2:36:49 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol

    28/04/2010 2:36:49 pm kernel AFP_VFS afpfs_unmount: /Volumes/Vol2, flags 524288, pid 629

    28/04/2010 2:36:49 pm kernel AFP_VFS afpfsCacheLookup: got 13 on root vnode, unmounting vol

    28/04/2010 2:36:49 pm kernel AFP_VFS afpfs_unmount: /Volumes/Vol1, flags 524288, pid 629

    28/04/2010 2:36:49 pm kernel AFP_VFS afpfs_mount: /Volumes/OurTimeCapsule, pid 40400

    One other thing that I have noticed recently (and seen on other systems) is that systems on the network seem to regularly get new names assigned to them with -1 or -2 appended. I don't know if this is connected to the problem or not, but it certainly could be part of the same syndrome. I get the impression that there's something going on somewhere in the code that handles network resources, maybe within Bonjour?

    One thing that I find highly frustrating is that even if you remount the network volume many apps (such as the MS Office 2008 and Adobe CS4 apps) crash and burn if they have a file open from it, and often in a somewhat untidy way - eg Word displays a dialog saying that the file may be corrupt with an OK button but if you press this the dialog disappears and reappears again straight away. there is no way to get out of this except by force-quitting, even though the app is actually running fine apart from being in an apparent deadlock.

  12. 0

    ernestal

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Very similar issues here over the past two days.

    We've experienced Four unmount events immediately after Time Machine began running.

    Time Machine has been disabled for now, and probably won't be coming back.

  13. 0

    Steven Slupsky

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have a mac mini SLS and since upgrading the server to 10.6.3, some clients cannot see the sharepoints. Weird though, some clients still do have access to the sharepoints. I've also had it reported that sometimes the sharepoints "come back".

  14. 0

    nxnw

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Exact same problem, happens intermittently right after daily time machine backup runs on the server. It has now happened twice, with 5 days in between occurrences.

    On the server, I get this error message:

    5/10/10 5:01:49 AM com.apple.launchd com.apple.console Warning
    (com.apple.DirectoryServices[29]) Job appears to have crashed: Abort trap
    5/10/10 5:01:49 AM com.apple.ReportCrash.Root com.apple.console Notice
    2010-05-10 05:01:49.940 ReportCrash[54643:2a03] Saved crash report for
    DirectoryService[29] version ??? (???) to
    /Library/Logs/DiagnosticReports/DirectoryService2010-05-10-050149localhost.crash

    This did not coincide with updating to 10.6.3. It started weeks later. The first occurrence, however, was during the first Time Machine backup after installing security update 2010-03.

  15. 0

    Daphoid

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thought I should chime in as well. I've got a Mac Mini (Early-2009) 2.0Ghz/4GB of RAM running Snow Leopard Server. This issue cropped up about a week ago. Every now and then (maybe twice a day?) I'll lose every AFP volume except the user folder when I login. All the other sharepoints disappear and are unaccessible via Connect to Server (afp://<IP>/<share>) as well. My current 'fix' is to open server admin, stop AFP then start it again and they come back to life.

    Luckily this is my home server so there's only 10 connections through my various boxes/VM's. In a business setting this would drive people crazy because after the restart of AFPD (I assume it's AFPd), I have to reconnect the share on all the clients.

    - D