mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 seems to ignore ECC errors
Date: Mon, 04 Aug 2008 18:12:54 +0200	[thread overview]
Message-ID: <jeiqugyd15.fsf@sykes.suse.de> (raw)
In-Reply-To: <20080804154727.GV4470@implementation.uk.xensource.com> (Samuel Thibault's message of "Mon, 4 Aug 2008 16:47:27 +0100")

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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2008-08-04 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 15:03 Samuel Thibault
2008-08-04 15:20 ` Samuel Thibault
2008-08-04 15:39 ` Andreas Schwab
2008-08-04 15:47   ` Samuel Thibault
2008-08-04 16:12     ` Andreas Schwab [this message]
2008-08-04 16:16       ` Samuel Thibault
2008-08-04 16:51     ` Theodore Tso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jeiqugyd15.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome