From: Paolo Bonzini <pbonzini@redhat.com>
To: mchristi@redhat.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi: add Synology to 1024 sector blacklist
Date: Tue, 12 Jan 2016 18:54:55 +0100 [thread overview]
Message-ID: <56953DEF.1050306@redhat.com> (raw)
In-Reply-To: <1452206045-18332-1-git-send-email-mchristi@redhat.com>
On 07/01/2016 23:34, mchristi@redhat.com wrote:
> From: Mike Christie <mchristi@redhat.com>
>
> Another iscsi target that cannot handle large IOs,
> but does not tell us a limit.
>
> The Synology iSCSI targets report:
>
> Block limits VPD page (SBC):
> Write same no zero (WSNZ): 0
> Maximum compare and write length: 0 blocks
> Optimal transfer length granularity: 0 blocks
> Maximum transfer length: 0 blocks
> Optimal transfer length: 0 blocks
> Maximum prefetch length: 0 blocks
> Maximum unmap LBA count: 0
> Maximum unmap block descriptor count: 0
> Optimal unmap granularity: 0
> Unmap granularity alignment valid: 0
> Unmap granularity alignment: 0
> Maximum write same length: 0x0 blocks
>
> and the size of the command it can handle seems to depend on how much
> memory it can allocate at the time. This results in IO errors when
> handling large IOs. This patch just has us use the old 1024 default
> sectors for this target by adding it to the scsi blacklist. We do
> not have good contacs with this vendors, so I have not been able to
> try and fix on their side.
Synology is just (an old fork of?) LIO. IIRC I saw similar problems a
couple years ago with LIO because iscsit_map_iovec maps everything a
page at a time and produced too large an iovec for the underlying
storage. I'm afraid you're going to get this for pretty much every user
of LIO.
Paolo
next prev parent reply other threads:[~2016-01-12 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 22:34 [PATCH 1/1] scsi: add Synology to 1024 sector blacklist mchristi
2016-01-08 2:44 ` Martin K. Petersen
2016-01-12 17:54 ` Paolo Bonzini [this message]
2016-01-13 9:33 ` Nicholas A. Bellinger
2016-01-13 9:41 ` Paolo Bonzini
2016-01-13 9:56 ` Nicholas A. Bellinger
2016-01-13 10:27 ` Paolo Bonzini
-- strict thread matches above, loose matches on Subject: below --
2015-05-22 19:22 michaelc
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=56953DEF.1050306@redhat.com \
--to=pbonzini@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mchristi@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 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).