Re: [PATCH] udev/mount.sh: try to kill active processes before umount

["John Willis" <John.Willis@Distant-earth.com>]

> >> Wouldn't a umount -l be a lot better in this case?
> >
> > I'm not sure if this would do the right things.
> >
> > mount.sh is called with REMOVE action when the device *is
> > disconnected* i.e. the filesystem is no longer available.
> > So i believe it is not possible to "cleanup all references to the
> > filesystem as soon as it is not busy anymore".
> >
> > I think killing all the processes is the only way here.
> 
> I don't like the idea of killing random processes, especially is that
process is
> smart enough to "move on" after a timeout.

I concur, the issue at hand is a little 'rock and a hard place' (what is the
'correct' way to deal with processes left over when the file system has most
definitely been pulled with prejudice ;)). Killing processes feels a little
wrong as a lot of apps can recover from filesystem pulls.

That said, we have been experimenting with umount -l on the OpenPandora with
some promising initial results. We are also playing with some other changes
that may also be of wider interest (mountpoints based on SD card labels if
they exist etc.). I'll keep this thread updated with the results of testing,
if it works out well I was going to suggest some of the changes for the
stock mount.sh.

There is little harm in a umount -l in the short term.

Regards,

John