public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Phillip Susi <phill@thesusis.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: Drive reset as an EH strategy when write cache is enabled
Date: Wed, 2 Dec 2020 15:03:30 +0000	[thread overview]
Message-ID: <20201202150330.GA25031@infradead.org> (raw)
In-Reply-To: <87r1o9phgd.fsf@vps.thesusis.net>

On Tue, Dec 01, 2020 at 12:24:50PM -0500, Phillip Susi wrote:
> A while back I noticed lines in my syslog indicating that a FLUSH CACHE
> command timed out and the drive was hard reset to recover.  That made me
> wonder if such a thing makes any sense as a valid EH strategy.  Any
> previous writes that returned successfully but are still sitting in the
> drive's write cache will be silently invalidated by resetting the drive
> won't they?  Then the FLUSH CACHE command is retried, and of course,
> succeeds because it is now a NOOP.  Then fsync() returns and postfix
> thinks my new email has been committed to the disk, when in fact, it has
> not.
> 
> Am I mistaken somewhere or is the kernel really doing the wrong thing
> here?

If the device drops the content of the volatile write on a reset we'll
have much problems than that..

  reply	other threads:[~2020-12-02 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01 17:24 Drive reset as an EH strategy when write cache is enabled Phillip Susi
2020-12-02 15:03 ` Christoph Hellwig [this message]
2020-12-02 15:55   ` Phillip Susi
2020-12-02 18:58     ` James Bottomley
2020-12-02 22:11       ` Phillip Susi

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=20201202150330.GA25031@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=phill@thesusis.net \
    /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