<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>loopkid: force unmount on mac os x</title>
    <link>http://loopkid.net/articles/2008/06/27/force-unmount-on-mac-os-x</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>sad songs make me happy</description>
    <item>
      <title>force unmount on mac os x</title>
      <description>&lt;p&gt;When using Mac OS X you might have encountered this message.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;The disk "foobar" is in use and could not be ejected.
Try quitting appplications and try again.
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This message may occur even if you have all closed all programs. The guilty party for this behavious may be Leopard&amp;#8217;s &lt;a href="http://developer.apple.com/documentation/Darwin/Conceptual/FSEvents_ProgGuide/Introduction/chapter_2_section_1.html"&gt;FSEvents&lt;/a&gt;, which sometimes has a lock on a volume. To force the unmount of a volume just open a Terminal and use umount.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;sudo umount -f /Volumes/FooBar
&lt;/code&gt;&lt;/pre&gt;</description>
      <pubDate>Fri, 27 Jun 2008 01:16:00 +0200</pubDate>
      <guid isPermaLink="false">urn:uuid:b9595033-68b0-4701-8893-ae22ea7a5407</guid>
      <author>Stefan</author>
      <link>http://loopkid.net/articles/2008/06/27/force-unmount-on-mac-os-x</link>
      <category>English</category>
      <category>Mac OS X</category>
      <trackback:ping>http://loopkid.net/articles/trackback/8395</trackback:ping>
    </item>
    <item>
      <title>"force unmount on mac os x" by Stefan</title>
      <description>&lt;p&gt;This works basically the same way on Mac OS X, but sometimes even changing the directory doesn&amp;#8217;t resolve the issue,&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# umount /Volumes/Foobar
umount: unmount(/Volumes/Foobar): Resource busy
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;then &lt;code&gt;diskutil&lt;/code&gt; comes to the help.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# diskutil umount /Volumes/Foobar
Volume Foobar on disk1s10 unmounted
&lt;/code&gt;&lt;/pre&gt;</description>
      <pubDate>Fri, 27 Jun 2008 12:30:09 +0200</pubDate>
      <guid isPermaLink="false">urn:uuid:29050922-887b-417f-97a6-d386e50f86ef</guid>
      <link>http://loopkid.net/articles/2008/06/27/force-unmount-on-mac-os-x#comment-8416</link>
    </item>
    <item>
      <title>"force unmount on mac os x" by b.</title>
      <description>&lt;p&gt;On linux machines it is often the case, that you are in the mounted directory when trying to unmount the device. Therefore you have to leave the directory to unmount the device:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# mount -o loop foo.iso /mnt
# cd /mnt/bar
# umount /mnt
umount: /mnt: device is busy
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;The man page tells us:
-f     Force unmount (in case of an unreachable NFS system).  (Requires kernel 2.1.116 or later.)&lt;/p&gt;

&lt;p&gt;The -f directive does not work in this case under linux machines. The umount command is still locked. So you have to leave the directory:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# cd /tmp
# umount /mnt
&lt;/code&gt;&lt;/pre&gt;</description>
      <pubDate>Fri, 27 Jun 2008 02:34:12 +0200</pubDate>
      <guid isPermaLink="false">urn:uuid:6a5661cc-061d-4bba-9df4-b544884f5b3c</guid>
      <link>http://loopkid.net/articles/2008/06/27/force-unmount-on-mac-os-x#comment-8400</link>
    </item>
  </channel>
</rss>
