site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com What happens when the Finder Eject button is pressed, and how can I register my filesystem's userspace client to receive notification when that happens so I can unmount? <http://developer.apple.com/technotes/tn2004/tn2124.html> S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 15:18 -0700 17/10/06, Michael Welch wrote: In contrast to mount, unmount is handled pretty much automatically by the system. The Finder calls File Manager (FSEjectVolumeSync/Async), which calls Disk Arb (DADiskUnmount, DADiskEject), which, to unmount the volume, fork/exec's <x-man-page://8/umount> (IIRC), which calls <x-man-page://2/unmount>, which does the unmount, calling your VFSOPUnmount entry point. Disk Arb also listens for unmount notifications via <x-man-page://3/notify_register_mach_port>. If a volume is unmounted outside of the scope of Disk Arb (you run "unmount" from the command line, say), Disk Arb will hear about it that way. If you file system has a user space helper daemon that needs to know about the unmounts of a particular file system, the best solution is to have your VFSOPUnmount routine notify your daemon through whatever communication channel it's using for general file system operations. This is exactly what WebDAV does. Check it out by searching the WebDAV source for "WEBDAV_UNMOUNT". The gotcha that I've encountered in getting unmount to work is that your mount tool has to call <x-man-page://3/realpath> on the mount point before passing it to <x-man-page://2/mount>. If you don't do this, it causes problems for <x-man-page://8/umount>. However, this wouldn't explain the hangs that you're seeing. To debug that, you probably should start by enabling DiskArb logging. Instruction for doing this are in the Technote 2124 "Mac OS X Debugging Magic". This email sent to site_archiver@lists.apple.com