lkml.org 
[lkml]   [2001]   [Sep]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Forced umount (was lazy umount)
From
Date
le mar 18-09-2001 at 01:21 Alex Stewart a écrit :
[...]
> I see no reason why a properly functioning system should ever need to
> truly force a umount. Under normal conditions, if one really needs to
> do an emergency umount, it should be possible to use fuser/kill/etc to
> clean up any processes using the filesystem from userland and then
> perform a normal umount to cleanly unmount the filesystem in question
> (or, with lazy umount, this could conceivably even be done in the
> reverse order). The only reason for really-I-mean-it-forcing a umount
> is if there is some problem which has caused one or more processes to
> get permanently stuck in a state where they can't be killed (i.e. D
> state), and thus can't release their hold on the filesystem.

Imagine you have a cdrom mounted with process reading it. You may want
to eject this cdrom without killing all processes, but just make them
know that there's an error somewhere, go read something else.
So it won't kill your shells, Nautilus/Konqueror, etc.

Xav



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:17    [W:0.071 / U:1.332 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site