From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Hugh Dickins <hugh@veritas.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][SCS] sd: Read Capacity if (16) fails
Date: Wed, 06 Aug 2008 12:44:16 -0400 [thread overview]
Message-ID: <yq1bq06w0tb.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1218040613.7493.13.camel@localhost.localdomain> (James Bottomley's message of "Wed\, 06 Aug 2008 09\:36\:53 -0700")
>>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:
James> On Wed, 2008-08-06 at 16:34 +0100, Hugh Dickins wrote:
>> PQual=0 Device_type=0 RMB=1 version=0x00 [no conformance claimed]
James> We could try using this as the trigger. I assume all DIF
James> supporting devices must also claim conformance to SPC3/SBC2 or
James> higher?
You'd think, wouldn't you?
Originally I only checked for PROTECT if version was SBC2 or better.
But as it turns out I have drives that only report SBC and yet they do
DIF. This old version is apparently reported to prevent problems in
other operating systems.
*sigh*
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2008-08-06 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:06 [PATCH][SCS] sd: Read Capacity if (16) fails Hugh Dickins
2008-08-06 14:25 ` Matthew Wilcox
2008-08-06 16:35 ` James Bottomley
2008-08-06 14:27 ` Martin K. Petersen
2008-08-06 15:34 ` Hugh Dickins
2008-08-06 16:36 ` James Bottomley
2008-08-06 16:44 ` Martin K. Petersen [this message]
2008-08-06 16:53 ` James Bottomley
2008-08-06 17:21 ` Hugh Dickins
2008-08-06 17:32 ` Martin K. Petersen
2008-08-06 17:36 ` James Bottomley
2008-08-06 16:44 ` 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=yq1bq06w0tb.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.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