From: Vladislav Bolkhovitin <vst-d+Crzxg7Rs0@public.gmane.org>
To: Chris Worley <worleys-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: scst-devel
<scst-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
OFED mailing list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: How do I get scst_vdisk/IB_SRP(T) to properly handle drives w/ 4KB sectors?
Date: Wed, 23 Jun 2010 21:08:51 +0400 [thread overview]
Message-ID: <4C223FA3.3090300@vlnb.net> (raw)
In-Reply-To: <AANLkTin2bONNlTF8mseOt3-pPcFF523-6EWHFD2XBOPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Chris Worley, on 06/22/2010 08:06 PM wrote:
> When given an LBA w/ a bad boundary, the drive returns an error and
> the target side says:
>
> dev_vdisk: ***ERROR***: cmd ffff810196f58b70 returned error -22
>
> ... and the initiator:
>
> sd 8:0:0:0: SCSI error: return code = 0x08000002
> sdc: Current: sense key: Medium Error
> Add. Sense: Unrecovered read error
>
> Is there a way to tell scst that this drive requires 4KB block sizes,
> and pass that upstream?
I'm not sure what you mean here under "tell" and "pass upstream".
Generally, such problems are outside of SCST scope and responsibilities.
With vdisk kernel I/O stack should make sure you use correct alignment
accessing your backend drive and you can always choose your own >512b
block size for all vdisk devices.
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-06-23 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 16:06 How do I get scst_vdisk/IB_SRP(T) to properly handle drives w/ 4KB sectors? Chris Worley
[not found] ` <AANLkTin2bONNlTF8mseOt3-pPcFF523-6EWHFD2XBOPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-23 17:08 ` Vladislav Bolkhovitin [this message]
[not found] ` <4C223FA3.3090300-d+Crzxg7Rs0@public.gmane.org>
2010-06-23 17:32 ` Chris Worley
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=4C223FA3.3090300@vlnb.net \
--to=vst-d+crzxg7rs0@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=scst-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=worleys-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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