Bug reports that are hardware failures masquerading as reiserfs bugs dominate our mailing list. We also get bug reports from users with versions that are prior to 2.4.4. We are now working on making the code more likely to identify a hardware failure as a hardware failure (without killing performance, which means there are many things we can do but we can't fully cure that problem). fsck is the one non-solid piece of our code, and that has greatly improved and will hopefully be solid by June 1. Two persons are working on it full-time. We have one bugfix in reiserfs that is not yet in the main kernel, mainly because it is a deep bugfix that we are being careful with so that it does not add more bugs. One user only so far has hit that bug. We have some new code that we are saving for 2.5.1, to relocate, resize, and generally tune the journal, and to mark blocks bad for users that need to do that for long enough to get a new disk drive (if you see bad blocks, usually your drive is no longer worth trusting your home directory to.) We will improve performance throughout 2.5, with a new block allocator and a journal tuning and relocation patch, being the most important changes likely to happen soon. All in all, things look good for starting work on reiser4 on June 1.:) Hans - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
