From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Hannes Reinecke <hare@suse.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SYNCHRONIZE_CACHE command is not retried
Date: Tue, 4 May 2010 14:53:11 +0200 [thread overview]
Message-ID: <201005041453.11308.bernd.schubert@fastmail.fm> (raw)
In-Reply-To: <4BE011AF.7010509@suse.de>
On Tuesday 04 May 2010, Hannes Reinecke wrote:
> Hi all,
>
> I'm facing an issue here where the 'SYNCHRONIZE CACHE' command is not
> retried:
Interesting that suddenly several people run into it, when I already noticed
long ago. Hmm, you work for Suse, maybe you now got the ticket I have asked
our customer about to open for their SLES system? ;)
Recent discussion is here:
http://kerneltrap.org/mailarchive/linux-scsi/2010/4/19/6884638
Sorry, I didn't have time yet to update the patch there.
Cheers,
Bernd
next prev parent reply other threads:[~2010-05-04 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 12:23 SYNCHRONIZE_CACHE command is not retried Hannes Reinecke
2010-05-04 12:53 ` Bernd Schubert [this message]
2010-05-04 13:07 ` Hannes Reinecke
2010-05-04 14:33 ` James Bottomley
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=201005041453.11308.bernd.schubert@fastmail.fm \
--to=bernd.schubert@fastmail.fm \
--cc=hare@suse.de \
--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