Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265632AbUAQGYK (ORCPT ); Sat, 17 Jan 2004 01:24:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265928AbUAQGYK (ORCPT ); Sat, 17 Jan 2004 01:24:10 -0500 Received: from mtaw6.prodigy.net ([64.164.98.56]:44241 "EHLO mtaw6.prodigy.net") by vger.kernel.org with ESMTP id S265632AbUAQGYI (ORCPT ); Sat, 17 Jan 2004 01:24:08 -0500 Date: Fri, 16 Jan 2004 22:23:51 -0800 From: Mike Fedyk To: Oleg Drokin Cc: Brad Tilley , Marcelo Tosatti , linux-kernel@vger.kernel.org Subject: Re: Possible Bug in 2.4.24???] Message-ID: <20040117062351.GU1748@srv-lnx2600.matchmail.com> Mail-Followup-To: Oleg Drokin , Brad Tilley , Marcelo Tosatti , linux-kernel@vger.kernel.org References: <514iaqBeC5488S07.1074301468@uwdvg007.cms.usa.net> <20040117051107.GC1967@linuxhacker.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040117051107.GC1967@linuxhacker.ru> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 741 Lines: 16 On Sat, Jan 17, 2004 at 07:11:07AM +0200, Oleg Drokin wrote: > Well, there was affect on filesystem - the write have failed. > Also may be later that block was remapped, or that was internal drive's logic > failure or something else like that. > This journal block won't be used on subsequent mount (because transaction > was not closed), but will be just > overwritten. So even if its content was corrupted, reiserfs does not care. I'd also suggest to brad that he replace the drive ASAP. Mike - 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/