On Fri, Dec 21, 2007 at 09:37:35AM +0100, Martin Pitt wrote: > We quickly discussed this at the last UDS. Most people were not in > favor of dropping the check completely, since occasionally, things > just go wrong, and you never notice until you actually run a check.
Any severe corruption is likely to trigger the kernel's own sanity checks, at which point a check will be forced anyway. Otherwise we seem to be optimising for a massively uncommon case at the expense of everyone else. If ext3 had a habit of introducing corruption, we'd know about it by now. We should just skip the time and count based checks. -- Matthew Garrett | [EMAIL PROTECTED] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
