"Expected behaviour" may be pushing it a bit, but you would experience
exactly the same thing on a Windows or Mac OS machine if you had a crash
whilst writing. The drive needs to be unmounted or "Safely removed"(to
use Windows terminology) in order to force it to flush the data. Using a
non-native file system wouldn't have helped matters either.

Moving forward:
Ideally use ext3 as your file system, or fat32 if you want Windows 
compatability.
Install the package "kerneloops" This will help provide debug information to 
help developers fix the crash.
Try and remember launchpad is for developers to discuss solutions not for 
throwing a hissy fit on the internet/digg.

I hope you recovered all your files successfully.

-- 
file move causes data loss if interrupted due to system crash
https://bugs.launchpad.net/bugs/303610
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to