From: joystick <joystick@shiftmail.org>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Write cache and surface error behaviour
Date: Sun, 20 Jul 2014 23:54:26 +0200 [thread overview]
Message-ID: <53CC3A92.5000501@shiftmail.org> (raw)
Hello list,
I don't really understand this disk cache thing.
Suppose a disk with write cache enabled of writeback type: Linux
receives a write completed notification (a message from the disk) when
the data has reached the cache of the disk. Correct? At that point it is
not considered an in-flight I/O anymore. Correct?
So what happens when the disk tries to write it to the platter and
discovers that there is a media error on that sector? (suppose
relocation does not happen ; maybe sectors exhausted)
Does Linux receive the write error upon the next flush it issues? So the
error is related to the flush? And what happens if Linux never issues
such flush?
Thank you
J.
next reply other threads:[~2014-07-20 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 21:54 joystick [this message]
2014-07-21 14:55 ` Write cache and surface error behaviour Dale R. Worley
2014-07-28 20:37 ` Dale R. Worley
2014-07-28 23:57 ` Jeremy Linton
2014-07-29 1:43 ` Douglas Gilbert
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=53CC3A92.5000501@shiftmail.org \
--to=joystick@shiftmail.org \
--cc=linux-scsi@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