Tom Zerucha <tz@execpc.com> wrote:
> For example, I start up xterm while my "current" directory is
> /mnt/floppy. I won't be able to umount the floppy until I kill the
> xterm, even if the new xterm chdir-s away from the floppy and doesn't
> have any open files.
Your shell changes it's current working directory, the xterm itself
doesn't.
> Currently I am running something that will take about an hour on a
> partition I really want to umount. Oops on my part, but there are NO
> open files (or lsof AND fuser are lying) on that partition. umount -f
> doesn't work (should it?).
>
> I can probably do the hack myself, but I was wondering what the best
> approach would be or if someone else out there has a patch or
> something. Adding a feature so umount -f would work as long as there
> were no open flies, just the unused "working" directory would suffice.
> Any suggestions or help would be welcome.
As long as the directory is the current working directory of any
process it isn't unused. So you can't umount the file system.
> For that matter, does umount -f do anything or work anywhere where
> umount wouldn't?
man umount:
-f Force unmount (in case of an unreachable NFS sys
tem). (Requires kernel 2.1.116 or later.)
Eilert
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Eilert Brinkmann -- Universitaet Bremen -- FB 3, Informatik
eilert@informatik.uni-bremen.de - eilert@tzi.org - eilert@linuxfreak.com
http://www.informatik.uni-bremen.de/~eilert/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Feb 07 2000 - 21:00:10 EST