https://bugzilla.kernel.org/show_bug.cgi?id=76261 --- Comment #10 from Theodore Tso <tytso@xxxxxxx> --- So see my earlier answer. If this is a normal shutdown, you must use syncfs() or the normal umount to unmount the file system. Emergency_remount is designed for emergencies when it may not be possible to do a blocking writeback. You could change emergency_remount to pass in a force value of 0 instead of 1. However, this will break non-android use cases where the system administrator really needs the current behaviour in a real emergency. Worse, even for the android use case, there may be times when there may be some kind of I/O error or other malfunction, where a blocking writeblock could stall the umount process indefinitely. So the right answer really is to use the algorithm I've outlined in comment #6. -- 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
