Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 28 Nov 2002 04:55:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 28 Nov 2002 04:55:48 -0500 Received: from angband.namesys.com ([212.16.7.85]:10884 "HELO angband.namesys.com") by vger.kernel.org with SMTP id ; Thu, 28 Nov 2002 04:55:48 -0500 Date: Thu, 28 Nov 2002 13:03:08 +0300 From: Oleg Drokin To: "Henning P. Schmiedehausen" Cc: linux-kernel@vger.kernel.org Subject: Re: reiserfs bug Message-ID: <20021128130308.A11579@namesys.com> References: <072801c296b8$2cb01000$6600a8c0@topconcepts.net> <20021128114755.A2724@namesys.com> <077201c296bb$43b4ac40$6600a8c0@topconcepts.net> <20021128115708.A2792@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.22.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 21 Hello! On Thu, Nov 28, 2002 at 09:13:43AM +0000, Henning P. Schmiedehausen wrote: > >Sorry, but you seems to have faulty hardware (bad harddrive or something). > >Reiserfs cannot tolerate bad blocks in journal area right now. > >I'd suggest you to make a backup of your device and then to replace bad > >harddrive. > You still shouldn't panic the kernel in this case. IMHO. Sure, panicking the kernel in case of a write error is not very nice thing to do. Jeff Mahoney (of SuSE) is working on improving this situation. He even released a preview patch some time ago (on 7th May). Bye, Oleg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/