On Wed, Jan 20, 2010 at 04:37:25PM -0600, Eric Sandeen wrote:
> From: Bill Nottingham <notting@xxxxxxxxxx>
>
> Anaconda has been setting the max mount count on the root fs
> to -1 (unused) for ages.
>
> I (Eric) tend to agree that using mount count as a proxy for potential
> for corruption seems odd. And waiting for fsck on a reboot just because
> it's number 20 (or so) is painful. Can we just turn it off by default?
>
> I wouldn't mind killing the periodic check as well, but consider
> this a trial balloon. :)
I think it would be better to make this be something tunable via
mke2fs.conf. And as a profile option, maybe we would want this to be
something where we periodically force a full fsck check and then send
TRIM commands down to the SSD. Given the size and speed of SSD's,
doing periodic TRIM's every N mounts mike actually be a good thing.
(It's dangerous to do a TRIM without doing a full fsck since if the
block allocation bitmap isn't quite right, the user could lose data.)
- 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
