Comment 16 for bug 198125

Seeing this exact problem in Ocelot. The filesystem on the external storage device is extremely upset that the device was ripped out from under it, and wasn't there yet (due to delay in the drive spinning up / enumerating) when the system was resumed. The system needs to delay suspending until all external storage devices are unmounted, and needs to NOT suspend if unmounting fails (due to a program/terminal/etc still being open somewhere pointing to these devices).

The current behavior of suspending regardless of external device state is WRONG and DOES result in data corruption. I don't understand why this is marked as 'Low priority'.