All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jambor <jamborm@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: What happens to pages that failed to be written to disk?
Date: Sat, 30 Jul 2005 21:47:36 +0200	[thread overview]
Message-ID: <8e70aacf050730124739a9382@mail.gmail.com> (raw)
In-Reply-To: <20050728003326.4add1a0f.akpm@osdl.org>

Hi and thanks for all answers.

On 7/28/05, Andrew Morton <akpm@osdl.org> wrote:
> > Is the error
> > somehow signalled to anyone?
> 
> Yes, it's propagated into the file's address_space for a later
> fsync()/fdatasync()/msync() to detect.

I see, so a subsequent sync, fsync or umount fail with an error even
when the writing that failed was not initiated because of them?

> > Do filesystems try to relocate the data
> > from bad blocks of the device?
> 
> Nope.  Disks will do that internally.  If a disk gets a write I/O error
> it's generally dead.

I am not interested in what happens in HW, I strive to write a filesystem :-) 
Anyway, I see that a write error probably does not happen because of
bad blocks anyway but because something even worse happened and
therefore there is no point in it even though our filesystem would be
able to relocate stuff fairly easily. Am I right?

Thanks again,

Martin

  parent reply	other threads:[~2005-07-30 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28  0:12 What happens to pages that failed to be written to disk? Martin Jambor
2005-07-28  7:33 ` Andrew Morton
2005-07-28  8:38   ` Szakacsits Szabolcs
2005-07-28 16:41     ` Bryan Henderson
2005-07-30 19:47   ` Martin Jambor [this message]
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=8e70aacf050730124739a9382@mail.gmail.com \
    --to=jamborm@gmail.com \
    --cc=akpm@osdl.org \
    --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.