public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: brace@hp.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org, mike.miller@hp.com
Subject: Re: [Question] Does the kernel ignore errors writng to disk?
Date: Thu, 28 Apr 2005 23:43:40 +0100	[thread overview]
Message-ID: <1114728218.18355.245.camel@localhost.localdomain> (raw)
In-Reply-To: <OFDD96A309.D5D89999-ON88256FF1.0062E298-88256FF1.00645C51@us.ibm.com>

On Iau, 2005-04-28 at 19:14, Bryan Henderson wrote:
> Probably the most common way to get the simple but slow write function 
> where the write() call actually writes to stable storage, and fails if it 
> can't, is the O_SYNC open flag.

O_SYNC doesn't work completely on several file systems and only on the
latest kernels with some of the common ones.

> But even that, in some versions of Linux, can miss write errors.  It's not 
> easy for Linux to catch them because the code that sees the I/O fail 
> doesn't know if it's part of some synchronous procedure where the user 
> will eventually find out about the error or the more common case where the 
> application has optimistically walked away and nothing can be done but 
> write off the loss.

Or because the error is reported out of order and there are ordering
guarantees in the fs. SCSI is ok here other controllers are not always
right.


  reply	other threads:[~2005-04-28 22:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-27 18:40 [Question] Does the kernel ignore errors writng to disk? mike.miller
2005-04-27 19:12 ` Richard B. Johnson
2005-04-28 14:58 ` Alan Cox
2005-04-28 18:14   ` Bryan Henderson
2005-04-28 22:43     ` Alan Cox [this message]
2005-04-28 23:14       ` Bryan Henderson
2005-04-29  7:25         ` Anton Altaparmakov
2005-04-29 19:11           ` Bryan Henderson
2005-04-29 22:00             ` Alan Cox
2005-04-30  0:41               ` Bryan Henderson
2005-05-01  9:01               ` Mogens Valentin
2005-04-28 23:22   ` Bartlomiej Zolnierkiewicz
2005-04-28 23:50     ` Alan Cox
2005-04-29  0:33       ` Bartlomiej Zolnierkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2005-04-28 15:05 Miller, Mike (OS Dev)

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=1114728218.18355.245.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=brace@hp.com \
    --cc=hbryan@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.com \
    /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