Open GoogleCodeExporter opened 8 years ago
> unmount failed
suggests that the user has preferred MacFusion to
Unmount on Sleep, Remount on Wake
Original comment by grahampe...@gmail.com
on 3 Jul 2007 at 9:34
> No files open
was probably not true if
> unmount failed
but we shouldn't see this as user error. It's sometimes not easy to tell which
files are open. For example: I recall that Microsoft Word could be
troublesome in terms of leaving files open even after Word had quit.
Initially I thought of using
lsof +D
but for MacFUSE volumes, normally
lsof: WARNING: can't stat(.): No such file or directory
Wiith reference to the manual page for
Note: the authority of the user of this option limits it
to searching for files that the user has permission to
examine with the system stat(2) function.
I guess, lsof might be used only when the allow_root option is specified -- but
allow_root is not recommended.
Original comment by grahampe...@gmail.com
on 3 Jul 2007 at 9:53
See also
MacFusion issue 25
<http://code.google.com/p/macfusion/issues/detail?id=25>
MacFusion issue 109
<http://code.google.com/p/macfusion/issues/detail?id=109>
MacFusion issue 145
<http://code.google.com/p/macfusion/issues/detail?id=145>
Original comment by grahampe...@gmail.com
on 3 Jul 2007 at 9:55
> Multiple attempts to unmount the drive return "the error unable to
> eject drive...". Ultimately the laptop has to be rebooted to remove
> the mount.
Landon: if you're happy working in Terminal, and if you find yourself in this
situation again, for the affected
file system please try the command
umount -f
(The command
mount
alone will present a list of currently mounted file systems.)
Original comment by grahampe...@gmail.com
on 3 Jul 2007 at 10:01
Addressed to the Google Group:
> Haven't been able to purposely repeat the error. I've
> probably made an assumption about the precondition that is
> not true. I'm going to re- evaluate the error next time it
> occurs in real world usage to confirm or deny this.
>
> Landon
Original comment by grahampe...@gmail.com
on 5 Jul 2007 at 1:35
Original issue reported on code.google.com by
grahampe...@gmail.com
on 3 Jul 2007 at 8:13