https://bugzilla.kernel.org/show_bug.cgi?id=25832 --- Comment #27 from Theodore Tso <tytso@xxxxxxx> 2011-02-07 15:35:59 --- There is shared umount code paths that are used by all file systems in fs/super.c, in the VFS layer, of course. But again, unless you or some userspace program has explicitly requested a umount, a umount does not happen just because a disk drive has disappeared. So if you are locking up right after a resume, there wouldn't have been any _time_ for you or some userspace program to request an umount. And certainly the standard desktop userspace programs (e.g., the GNOME desktop) do not automagically look for kernel I/O error messages caused by a disk disappearing, and then umount the file system automagically. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
