From: Ross Biro <rossb@google.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Failed writes marked clean?
Date: Fri, 08 Nov 2002 13:30:41 -0800 [thread overview]
Message-ID: <3DCC2D01.6050309@google.com> (raw)
In-Reply-To: 3DCC252F.65C0F70B@digeo.com
Andrew Morton wrote:
>Also, think about what a write error _means_. Unless the disk is truly
>ancient, it means that the device has run out of alternate space for
>the block, or all writes are failing. ie: it is a serious failure.
>
>
I've seen all sorts of interesting drive failure modes, including losing
communications with the drive for a short period and then having it come
back almost as good as new. We've had some data corruption on flaky
drives and I'm guessing this has something to do with it.
I'm going to sit down with our application developers and see what they
want to see from their end and see what I can do.
Ross
next prev parent reply other threads:[~2002-11-08 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 20:29 [BUG] Failed writes marked clean? Ross Biro
2002-11-08 20:53 ` Linus Torvalds
2002-11-08 20:57 ` Andrew Morton
2002-11-08 21:30 ` Ross Biro [this message]
2002-11-08 23:35 ` Theodore Ts'o
2002-11-09 1:29 ` Bernd Eckenfels
2002-11-12 20:04 ` Pavel Machek
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=3DCC2D01.6050309@google.com \
--to=rossb@google.com \
--cc=akpm@digeo.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