From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262356AbTJNKbl (ORCPT ); Tue, 14 Oct 2003 06:31:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262360AbTJNKbl (ORCPT ); Tue, 14 Oct 2003 06:31:41 -0400 Received: from thebsh.namesys.com ([212.16.7.65]:47594 "HELO thebsh.namesys.com") by vger.kernel.org with SMTP id S262356AbTJNKbi (ORCPT ); Tue, 14 Oct 2003 06:31:38 -0400 Message-ID: <3F8BD085.6020107@namesys.com> Date: Tue, 14 Oct 2003 14:31:33 +0400 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rogier Wolff CC: John Bradford , Wes Janzen , linux-kernel@vger.kernel.org Subject: Re: Why are bad disk sectors numbered strangely, and what happens to them? References: <200310131014.h9DAEwY3000241@81-2-122-30.bradfords.org.uk> <33a201c39174$2b936660$5cee4ca5@DIAMONDLX60> <20031014064925.GA12342@bitwizard.nl> <3F8BA037.9000705@sbcglobal.net> <200310140721.h9E7LmNE000682@81-2-122-30.bradfords.org.uk> <20031014074020.GC13117@bitwizard.nl> <200310140811.h9E8Bxq1000831@81-2-122-30.bradfords.org.uk> <3F8BB7AE.2040507@namesys.com> <20031014094629.GA16683@bitwizard.nl> <3F8BC896.6020106@namesys.com> <20031014101021.GE16683@bitwizard.nl> In-Reply-To: <20031014101021.GE16683@bitwizard.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Rogier Wolff wrote: >On Tue, Oct 14, 2003 at 01:57:42PM +0400, Hans Reiser wrote: > > >>Rogier Wolff wrote: >> >> >>>Of course, I left my drive that indicated it had problems (i.e. it >>>didn't spot the sector going bad before it became unreadable), in the >>>machine for another two days. It's getting replaced ASAP (i.e. the >>>next hour or so). >>> >>> > > > >>replacing the drive is reasonable caution. I think though that the >>other poster is right that IFF you want to remap bad blocks, the drive >>should do it not reiserfs. >> >> > >It is a "pretty much for free" feature. In your in-kernel >implementation you hopefully already have the ability to skip blocks >in use by other files. So allocating it to a special file will take >care of the kernel part. Next you need one line in your fsck to >prevent that "dangling inode" getting linked into lost+found. Then you >do need a utility to actually be able to mark blocks as bad. > > Roger. > > > We DO have it. It is present in Reiser4, and there is a patch around somewhere for V3 that I would be happy to have someone merge into the latest V3 code and test (we are too focused on shipping V4 to do it ourselves right now). I agree that the FS should be able to do it, but I also think that the drive doing it is best. -- Hans