On Fri, Aug 05, 2016 at 09:29:59AM +0300, Nikolay Borisov wrote: > > The easist way to fix this is defer the ext4_commit_super() to a > > workqueue. We only need this in the errors=continue case, and in that > > scenario we're not in a hurry when the superblock gets written out. > > Is errors=continue the default option if nothing specifically is > specified at mount time, since I don't have this set explicitly: > > /dev/vda / ext4 rw,relatime,data=ordered 0 0 Yes, it's the default. I keep wondering whether we should change the default to remount-ro or even panic, since people sometimes don't notice that the "file system has been corrupted" messages, and then they can end up losing a lot more detail if we forced them to address the issue right away. - Ted -- 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
