From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Masover Subject: Re: I request inclusion of reiser4 in the mainline kernel Date: Tue, 20 Sep 2005 09:41:36 -0500 Message-ID: <43301FA0.7030906@slaphack.com> References: <200509182004.j8IK4JNx012764@inti.inf.utfsm.cl> <432E5024.20709@namesys.com> <20050920075133.GB4074@elf.ucw.cz> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <20050920075133.GB4074@elf.ucw.cz> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: Pavel Machek Cc: Hans Reiser , Horst von Brand , thenewme91@gmail.com, Christoph Hellwig , Denis Vlasenko , chriswhite@gentoo.org, LKML , ReiserFS List Pavel Machek wrote: > Hi! > > >>V3 is obsoleted by V4 in every way. V3 is old code that should be >>marked as deprecated as soon as V4 has passed mass testing. V4 is far >>superior in its coding style also. Having V3 in and V4 out is at this >>point just stupid. > > > Really? Last time I checked, even V3's fsck was not too great. [In > fact I never could make it run stable enough to even _test_ it > properly]. > > Do you have working fsck for V4? Already saved me once. But then, I should have had backups. And personally, if it was my FS, I'd stop working on fsck after it was able to "check". That's what it's for. To fix an FS, you wipe it and restore from backups.