I second that, I can understand the behaviour on servers or other mission critical systems, but there seems to be no point forcing an fsck for such an issue on either desktops or mobile systems. Would be cool to be able to enable/disable this feature with a mount option (eg. mount=ignore_superbock_timestamp,defaults).
I second that, I can understand the behaviour on servers or other mission critical systems, but there seems to be no point forcing an fsck for such an issue on either desktops or mobile systems. Would be cool to be able to enable/disable this feature with a mount option (eg. mount=ignore_ superbock_ timestamp, defaults) .