Synopsis: [usb] [reboot] instant system reboot when unmounting a powered
off/unplugged+replugged USB device
State-Changed-From-To: suspended-closed
State-Changed-By: eadler
State-Changed-When: Thu Sep 29 14:36:28 UTC 2011
State-Changed-Why:
The cause of this issue is believed to have been in
On Sun, 2008-01-27 at 14:29 +1100, Peter Jeremy wrote:
This approach doesn't work because GEOM doesn't know the drive has
gone away until it's no longer present. At that point it's too late
to write unflushed buffers. And a devfs-triggered forced unmount does
not address the issue of
In message: [EMAIL PROTECTED]
Henrik Gulbrandsen [EMAIL PROTECTED] writes:
: On Sat, 2008-01-26 at 20:40 -0700, M. Warner Losh wrote:
: One of the things that I've been working on with someone (whose name
: escapes me) and Bruce Evans is trying to address these issues. One
:
On Sat, 2008-01-26 at 00:34 +, [EMAIL PROTECTED] wrote:
This is a well-known error: there are underlying structures in the kernel
that haven't been made to understand that drives can go away. This
assumption has been false for years. However, the work required is going
to be quite
On Sat, Jan 26, 2008 at 12:54:54PM +0100, Henrik Gulbrandsen wrote:
At this point, only the file systems need to be updated. The cleanest
way to handle things may be to have GEOM automatically unmount them at
orphaning. Until that's done, however, unmounting from user space via
devd seems to be a
In message: [EMAIL PROTECTED]
Peter Jeremy [EMAIL PROTECTED] writes:
: On Sat, Jan 26, 2008 at 12:54:54PM +0100, Henrik Gulbrandsen wrote:
: At this point, only the file systems need to be updated. The cleanest
: way to handle things may be to have GEOM automatically unmount them at
:
