I've made some changes to ext2 filesystem, and its approaching stability but not yet there. The problem is that I see corruptions after the FS has been mounted and running for days, but not immediately. The other problem is these corruptions don't show up on our test environment, and only on customer environments whether they have been running for days. In such a condition, it is difficult to log the results of the algorithms that execute millions of times a minute, the resulting log output would be too large to analyze, plus the latencies introduced with kernel logging (logging of all block operations) would make it impossible to run in production. My question is, Is there a better way (better than logging) of tracking operations internal to the kernel continuously over long period of time in a way that doesn't affect latency (very drastically)? Thanks, -Joel -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
