Hi Ted, Thanks for the quick response.
On Mon, 2007-03-05 at 11:48 -0500, Theodore Tso wrote: > Actually, power loss by itself should *not* cause any corruption when > you are using ext3; that's the whole point of the journal. If there > is, you probably have some other problem that you might do well to try > to debug before youi ship your product, since that may lead to > significant data loss in the long-term. OK. I do need to do further testing to see how well the system copes in situations like this, understanding e2fsck's behaviour is just a starting point. In the quoted section above, do you regard 'preen-mode not automatically fixing everything' and 'corruption' as the same? i.e. are you saying that the "UNEXPECTED INCONSISTENCY" error message should never appear after an unexpected power loss? Alternatively, in which kinds of situations would you reasonably expect preen mode to not be able to automate all the repairs? I realise that I mentioned corruption in my last mail, but actually I don't think we have really seen any of that. Instead the biggest issue right now is e2fsck halting system boot, and I definitely have seen this happen a few times (even if no damage was observed after re-running fsck with -y) Thanks. -- Daniel Drake Brontes Technologies, A 3M Company - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
