From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1758362AbYHDQRA@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1758362AbYHDQRA (ORCPT <rfc822;w@1wt.eu>);
	Mon, 4 Aug 2008 12:17:00 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756033AbYHDQQp
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 4 Aug 2008 12:16:45 -0400
Received: from smtp.eu.citrix.com ([62.200.22.115]:12980 "EHLO
	SMTP.EU.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755734AbYHDQQo (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 4 Aug 2008 12:16:44 -0400
X-IronPort-AV: E=Sophos;i="4.31,305,1215388800"; 
   d="scan'208";a="1278214"
Date: Mon, 4 Aug 2008 17:16:26 +0100
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Andreas Schwab <schwab@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 seems to ignore ECC errors
Message-ID: <20080804161626.GZ4470@implementation.uk.xensource.com>
Mail-Followup-To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Andreas Schwab <schwab@suse.de>, linux-kernel@vger.kernel.org
References: <20080804150353.GS4470@implementation.uk.xensource.com> <je8wvczt5x.fsf@sykes.suse.de> <20080804154727.GV4470@implementation.uk.xensource.com> <jeiqugyd15.fsf@sykes.suse.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <jeiqugyd15.fsf@sykes.suse.de>
User-Agent: Mutt/1.5.12-2006-07-14
X-OriginalArrivalTime: 04 Aug 2008 16:16:26.0559 (UTC) FILETIME=[720034F0:01C8F64D]
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Andreas Schwab, le Mon 04 Aug 2008 18:12:54 +0200, a écrit :
> Samuel Thibault <samuel.thibault@ens-lyon.org> writes:
> 
> > Andreas Schwab, le Mon 04 Aug 2008 17:39:06 +0200, a écrit :
> >> Samuel Thibault <samuel.thibault@ens-lyon.org> writes:
> >> > However, to my surprise Linux (2.6.26) continued to mount the ext3
> >> > filesystem read/write, spitting out a lot of IDE errors.  Shouldn't
> >> > filesystems remount read-only and let the admin try to save data in such
> >> > case?
> >> 
> >> That's a tunable parameter of the filesystem, see tune2fs(8).
> >
> > Oh, I had assumed it was on by default, hum.  But now it reads
> >
> > Errors behavior:          Remount read-only
> >
> > and I am still getting the same behavior.  Indeed after some VFS
> > modifications time it gets remounted read-only, but shouldn't that
> > happen as soon as possible?
> 
> The block device may do some retries before passing the error on.

Sure.  But I forgot to mention that after spitting all these write
errors, the filesystem remains mounted read-write.

Samuel