From: Christoph Hellwig <hch@lst.de>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>,
Nicholas Bellinger <nab@linux-iscsi.org>
Cc: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: block: remove artifical max_hw_sectors cap
Date: Tue, 23 Dec 2014 09:28:05 +0100 [thread overview]
Message-ID: <20141223082805.GA2303@lst.de> (raw)
In-Reply-To: <5497F319.20802@profihost.ag>
On Mon, Dec 22, 2014 at 11:31:53AM +0100, Stefan Priebe - Profihost AG wrote:
> Hi,
>
> since the below patch i've some problems with iscsi.
>
> The LIO based iscsi Server is full of messages like this:
> SCSI OP 2ah with too big sectors 8344 exceeds fabric_max_sectors: 8192
>
> And the client says:
> Buffer I/O error on device sdd, logical block 38861907
> lost page write due to I/O error on sdd
>
> May be some code fixes for iscsi client is missing?
No, the problem seems that the the target is enforcing a size limit
without communicating it through the block limits EVPD page.
Nic, can you fix LIO to expose the proper max xfer size?
next parent reply other threads:[~2014-12-23 8:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5497F319.20802@profihost.ag>
2014-12-23 8:28 ` Christoph Hellwig [this message]
2014-12-28 12:08 ` block: remove artifical max_hw_sectors cap Stefan Priebe
2014-12-30 11:32 ` Christoph Hellwig
2014-12-30 14:15 ` Stefan Priebe - Profihost AG
2015-01-05 17:17 ` Christoph Hellwig
2015-01-05 18:40 ` Stefan Priebe
2015-01-06 22:39 ` Nicholas A. Bellinger
2015-01-06 23:41 ` Nicholas A. Bellinger
2015-01-07 14:31 ` Christoph Hellwig
2015-01-07 14:32 ` Stefan Priebe - Profihost AG
2015-01-07 14:37 ` Christoph Hellwig
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=20141223082805.GA2303@lst.de \
--to=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=s.priebe@profihost.ag \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).