public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Johann Lombardi <johann@clusterfs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Clear PG_error before reading a page
Date: Thu, 17 May 2007 09:47:30 -0700	[thread overview]
Message-ID: <20070517094730.5cdfaa64.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070517114250.GA2141@chiva>

On Thu, 17 May 2007 13:42:50 +0200 Johann Lombardi <johann@clusterfs.com> wrote:

> > What is the actual real-world operational scenario here?  Would it be a
> > hotplugged disk?  A transient network failure in a SAN?  IOW, is it
> > something from which the kernel should automatically recover, or it is a
> > situation in which manual intervention would be better?
> 
> The real-world operational scenario is a storage system reporting medium
> errors which can be corrected by a manual intervention.

So running ioctl(BLKFLSBUF) against the device will fix things up?

Perhaps not, and we should invalidate all the file data as well. The
only ways we have of doing that are umount+mount or /proc/sys/vm/drop_caches.

I'm not sure what is the best thing to do here - there are advantages to
caching the fact that the device (or some of it) is unreadable.

  reply	other threads:[~2007-05-17 16:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 14:37 Clear PG_error before reading a page Johann Lombardi
2007-05-15 17:11 ` Andrew Morton
2007-05-15 21:01   ` Johann Lombardi
2007-05-15 21:23     ` Andrew Morton
2007-05-16 15:39       ` Johann Lombardi
2007-05-16 15:49         ` Nick Piggin
2007-05-16 16:12         ` Andrew Morton
2007-05-17 11:42           ` Johann Lombardi
2007-05-17 16:47             ` Andrew Morton [this message]
2007-05-29 17:06               ` Johann Lombardi

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=20070517094730.5cdfaa64.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=johann@clusterfs.com \
    --cc=linux-kernel@vger.kernel.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