On Mon, 28 Dec 2015 11:20:33 -0500
Hendrik Boom <hendrik@???> wrote:

> On Mon, Dec 28, 2015 at 05:17:01PM +0100, Didier Kryn wrote:
> > Le 28/12/2015 14:29, Simon Hobson a écrit :
> > >Didier Kryn<kryn@???> wrote:
> > >
> > >>>There remains a fundamental problem with automatic mount/umount.
> > >>>While automounting is safe, auto-unmounting is not if it is
> > >>>triggered by device removal. Unmounting must be done*before*
> > >>>removing the device if anything has been written to it,
> > >>>otherwise data is lost and the filesystem may be corrupted; also
> > >>>running applications with open files in the mountpoint can
> > >>>broken.
> > >Indeed
> > >
> > >>>auto-unmounting is not if it is triggered by device removal.
> > >But there is a slight issue in that if the user has yanked the
> > >drive, there isn't much you can do about it. Short of having
> > >precognition so you know in advance, or modifying all hardware to
> > >support locking the drive in, once the drive is disconnected then
> > >you have no options - other than to tell the user off.
> >
> > For this reason, the automounter package should provide a command
> > for the user to "safely remove the devices". Not providing it would
> > suggest the user that removing the device right away is harmless and
> > is the normal way.
>
> And the command to safely remove the devices should be easily
> discoverable. Once we re using automount, we are talking about tools
> that can be used by idiots.

Yeah, I can do all this in a future (but not too distant) version, with
use of a second program. Perhaps instead of running it out of runit or
inittab's respawn or /etc/rc.local, it should be run out of the
"client" program.

SteveT

Steve Litt 
November 2015 featured book: Troubleshooting Techniques
     of the Successful Technologist
http://www.troubleshooters.com/techniques