Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 1 Dec 2001 19:08:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 1 Dec 2001 19:08:32 -0500 Received: from krusty.E-Technik.Uni-Dortmund.DE ([129.217.163.1]:28941 "EHLO krusty.e-technik.uni-dortmund.de") by vger.kernel.org with ESMTP id ; Sat, 1 Dec 2001 19:08:26 -0500 Date: Sun, 2 Dec 2001 01:08:23 +0100 From: Matthias Andree To: linux-kernel@vger.kernel.org Subject: Re: Journaling pointless with today's hard disks? Message-ID: <20011202010823.A5653@emma1.emma.line.org> Mail-Followup-To: linux-kernel@vger.kernel.org In-Reply-To: <01112715312104.01486@localhost> <20011128194302.A29500@emma1.emma.line.org> <01112813462404.01163@driftwood> <20011128231925.A7034@emma1.emma.line.org> <20011129232157.A211@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20011129232157.A211@elf.ucw.cz> User-Agent: Mutt/1.3.22.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 29 Nov 2001, Pavel Machek wrote: > > Drives should never reassign blocks on read operations, because they'd > > take away the chance to try to read that block for say four hours. > > Why not? If drive gets ECC-correctable read error, it seems to me like > good time to reassign. Because you don't know if it's just some slipped bits, a shutdown during write, or an actual fault. When that happens on a verify after write, that's indeed reasonable. Otherwise the drive should just mark that block as "watch closely on next write". - 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/