public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Mon, 4 Aug 2008 17:16:26 +0100	[thread overview]
Message-ID: <20080804161626.GZ4470@implementation.uk.xensource.com> (raw)
In-Reply-To: <jeiqugyd15.fsf@sykes.suse.de>

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

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04 15:03 ext3 seems to ignore ECC errors 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
2008-08-04 16:16       ` Samuel Thibault [this message]
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=20080804161626.GZ4470@implementation.uk.xensource.com \
    --to=samuel.thibault@ens-lyon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@suse.de \
    /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