On Wed, Feb 16, 2011 at 12:14:33PM -0600, Eric Sandeen wrote:
> The forced fsck often comes at unexpected and inopportune moments,
> and even enterprise customers are often caught by surprise when
> this happens. Because a filesystem with an error condition will
> be marked as requiring fsck anyway, I submit that the time-based
> and mount-based checks are not particularly useful, and that
> administrators can schedule fscks on their own time, or tune2fs
> the enforced intervals if they so choose. Patch #1 disables the
> intervals by default, and I've added a new mkfs option (-C) to
> turn on the old behavior of random, unexpected, time-consuming
> fscks at boot time. ;)
>
> Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx>
How about just making it be an /etc/mke2fs.conf profile. Just use
something like this:
get_bool_from_profile(fs_types, "enable_periodic_fsck", 0)
... and I don't think we need to have a new command-line option.
People who want old behaviour can do
[defaults]
enable_period_fsck = true
- 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
