https://bugzilla.kernel.org/show_bug.cgi?id=93031 Andrey Lelikov <bugzillakernel1@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugzillakernel1@xxxxxxxxx --- Comment #3 from Andrey Lelikov <bugzillakernel1@xxxxxxxxx> --- I also experience same behaviour. The system is unbootable. Please note, that i do NOT have journal_checksum in fstab. On a kernel that works I have the following: /etc/fstab: /dev/mapper/root_crypt / ext4 errors=remount-ro,data=writeback,noatime,nobarrier,journal_async_commit,commit=120,dioread_nolock /proc/mounts: /dev/disk/by-uuid/a3dc1a73-42b9-4295-b0b0-93934b57d317 / ext4 rw,noatime,dioread_nolock,journal_checksum,journal_async_commit,nobarrier,errors=remount-ro,commit=120,data=writeback On 3.18 (ubuntu trusty) I can't boot any way - regular boot fails to mount, mount -o remount doesn't work with any options - with or without journal_async_commit and/or journal_checksum. Note that on 3.13 everything works, all flags are properly applied and they are NOT silently ignored. So this is a bug, but it is yet in denial stage. "remove journal_checksum from fstab, or add it to rootflags, everything works, la-la-la". Pedantic idiots. -- 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
