From: Douglas Gilbert <dgilbert@interlog.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linux SCSI Mailing list <linux-scsi@vger.kernel.org>
Subject: Re: sd: protection difficulties
Date: Thu, 17 Nov 2011 12:54:56 -0500 [thread overview]
Message-ID: <4EC54A70.20406@interlog.com> (raw)
In-Reply-To: <yq1vcqifzt5.fsf@sermon.lab.mkp.net>
On 11-11-17 12:01 PM, Martin K. Petersen wrote:
>>>>>> "Doug" == Douglas Gilbert<dgilbert@interlog.com> writes:
>
> Doug,
>
> Doug> Now with zeros filling the user data part of each logical block
> Doug> and a LB guard field of 0xffffffff that means any attempt to read
> Doug> a LB before it is written will result in an error like this [lk
> Doug> 3.1.0]:
> Doug> sd 6:0:0:0: [sdb]
> Doug> Target Data Integrity Failure
> Doug> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Sense Key :
> Doug> Aborted Command [current] Add. Sense: Logical block guard
> Doug> check failed CDB: Read(10): 28 20 00 00 00 00 00 00 08 00
> Doug> end_request: I/O error, dev sdb, sector 0
>
> I'm guessing you are using an mpt2sas with recent firmware?
Yes:
mpt2sas version 09.100.00.00 loaded
Whenever I report a bug to LSI (who are much better
than most) they always say to upgrade to the latest
firmware and re-test :-)
LSI changed
> behavior to always check PI even when the app tag contains 0xFFFF (which
> means "don't check" this block).
That useful piece of information is well hidden!
[sbc3r29.pdf section 4.21.3 top of page 61]
You learn something every day.
> I have some patches that LSI haven't signed off on yet. Which is why I
> haven't posted them...
Hopefully this thread expedites matters.
Doug Gilbert
prev parent reply other threads:[~2011-11-17 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 16:31 sd: protection difficulties Douglas Gilbert
2011-11-17 17:01 ` Martin K. Petersen
2011-11-17 17:54 ` Douglas Gilbert [this message]
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=4EC54A70.20406@interlog.com \
--to=dgilbert@interlog.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).