All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: What happens to pages that failed to be written to disk?
Date: Thu, 28 Jul 2005 02:12:42 +0200	[thread overview]
Message-ID: <8e70aacf05072717125bfc1c58@mail.gmail.com> (raw)

Hi,

I have tried to find out how filesystems are supposed to handle the
situation when an asynchronous writeout of a page fails and so had a
look at the ext2 code. All I have found is that for example
mpage_end_io_write sets the Error flag of both the page and its
mapping... and that is about it. What happens to these pages later on?
Does the memory manager attempt to write them again? Is the error
somehow signalled to anyone? Do filesystems try to relocate the data
from bad blocks of the device?

TIA

Martin Jambor

             reply	other threads:[~2005-07-28  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28  0:12 Martin Jambor [this message]
2005-07-28  7:33 ` What happens to pages that failed to be written to disk? Andrew Morton
2005-07-28  8:38   ` Szakacsits Szabolcs
2005-07-28 16:41     ` Bryan Henderson
2005-07-30 19:47   ` Martin Jambor
2005-07-30 21:13     ` Anton Altaparmakov

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=8e70aacf05072717125bfc1c58@mail.gmail.com \
    --to=jamborm@gmail.com \
    --cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.