From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Oglesby Subject: Re: I request inclusion of reiser4 in the mainline kernel Date: Sun, 18 Sep 2005 16:43:22 -0500 Message-ID: <432DDF7A.3050704@teleformix.com> References: <200509182004.j8IK4JNx012764@inti.inf.utfsm.cl> <432DCE2A.5070705@slaphack.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <432DCE2A.5070705@slaphack.com> List-Id: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: David Masover Cc: Horst von Brand , thenewme91@gmail.com, Christoph Hellwig , Denis Vlasenko , chriswhite@gentoo.org, Hans Reiser , LKML , ReiserFS List David Masover wrote: > Horst von Brand wrote: > >> There are lots of reports of ReiserFS 3 >> filesystems completely destroyed by minor hardware flakiness. > > > Honestly, this is one of the things I like about Linux. If I have > memory errors, Windows will just keep running, occasionally something > will crash, you restart it, never suspecting just how corrupt things > are getting under the hood. On Linux, I generally get kernel panics > pretty quickly, so I run memtest86 and replace the RAM. > > If my hardware is flaky, I consider it my job to replace it, not the > job of all my software to magically compensate for it. If I lose > data, oh well, I have backups. If I didn't, I was asking for trouble > anyway. I'm of the same opinion. If I have hardware that has a problem, and causes downtime, it gets replaced or repaired. I don't switch to a different piece of software to compensate for broken hardware. With that said, I have seen ReiserFS expose hardware that had problems. Hardware was repaired, and ReiserFS rides again. --Dan