From: Jeremy Linton <jlinton@tributary.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "emilne@redhat.com" <emilne@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"dgilbert@interlog.com" <dgilbert@interlog.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>
Subject: Re: [dm-devel] SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails]
Date: Tue, 24 Sep 2013 14:12:34 -0500 [thread overview]
Message-ID: <5241E422.1010700@tributary.com> (raw)
In-Reply-To: <52412581.2010909@suse.de>
On 9/24/2013 12:39 AM, Hannes Reinecke wrote:
> My drives support 'report opcodes', and report that write same is
> supported: ... 93 16 Write same(16) ...
>
> but no support for page 'b0'. And yes, these are real SAS drives.
So the question is, how many devices get the protect bit in the std inquiry
incorrect?
If that is mostly correct, how about std inquiry (SPC>2), protect bit, and then
VPD page 0x86 (or alternatively then do the READ CAPACITY, P_TYPE instead of
page 0x86)?
After all, the set of valid read/write opcodes is limited by the protection
mode format, yes?
next prev parent reply other threads:[~2013-09-24 19:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 16:13 [PATCH] dm mpath: disable WRITE SAME if it fails Mike Snitzer
2013-09-20 21:21 ` SCSI's heuristics for enabling WRITE SAME still need work [was: dm mpath: disable WRITE SAME if it fails] Mike Snitzer
2013-09-20 22:03 ` Martin K. Petersen
2013-09-21 15:28 ` Douglas Gilbert
2013-09-23 18:18 ` Ewan Milne
2013-09-24 5:39 ` [dm-devel] " Hannes Reinecke
2013-09-24 12:34 ` Mike Snitzer
2013-09-24 13:49 ` Martin K. Petersen
2013-09-24 15:15 ` Mike Snitzer
2013-09-25 20:52 ` Bernd Schubert
2013-09-25 22:12 ` Douglas Gilbert
2013-09-26 0:44 ` Martin K. Petersen
2013-09-26 5:39 ` Douglas Gilbert
2013-09-26 13:41 ` Bernd Schubert
2013-09-26 14:42 ` Martin K. Petersen
2013-09-26 15:34 ` Bernd Schubert
2013-09-26 15:47 ` Douglas Gilbert
2013-09-26 18:42 ` Saxena, Sumit
2013-09-24 19:12 ` Jeremy Linton [this message]
2013-09-24 19:37 ` [dm-devel] " Douglas Gilbert
2013-09-24 9:37 ` Paolo Bonzini
2013-09-24 13:25 ` James Bottomley
2013-09-24 18:39 ` [dm-devel] " Mikulas Patocka
2013-09-24 20:44 ` Martin K. Petersen
2013-09-24 22:02 ` Mike Snitzer
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=5241E422.1010700@tributary.com \
--to=jlinton@tributary.com \
--cc=dgilbert@interlog.com \
--cc=dm-devel@redhat.com \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=snitzer@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.