On Mon, Jul 28, 2014 at 11:11:45AM +0200, Lukáš Czerner wrote: > > I very much agree with that, that's why I was quite surprised that I > found out recently that this is the default. I was living in the > delusion that the default was ERRORS_RO for as long as I can remember. > So my question is, should we change it ? This really does not seem > like a sane default. Yeah, I've been thinking that this would be a good thing to change for 1.43. The only reason that errors=continue was the default was for historical reasons. I could imagine some system administrators being surprised when all of a sudden their production systems start getting lots of EROFS errors getting reported by applications. So I could potentially imagine some Help Desks / Support folks at distributions not being enthusiastic about such a change. Hmm.... we are starting to have some errors where we can allow the system to stagger on, even if we need to disallow new allocations in some block groups. I wonder if it is worthwhile to have a "continue for correctable errors". The danger, of course, is that some errors, even if they are correctable, (such as freeing a block which is already freed), could be a hint that there are other fs corruptions, not yet detected, that might lead to data loss if we reboot and fsck, or remount readonly right away. So the question is while there is some value, is it worth the added complexity to add an "errors=continue-correctable" option? - 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
