diff options
author | Mike Christie <mchristi@redhat.com> | 2016-01-08 01:34:05 +0300 |
---|---|---|
committer | Martin K. Petersen <martin.petersen@oracle.com> | 2016-01-08 05:43:26 +0300 |
commit | 9055082fb100cc66e20c048251d05159f5f2cfba (patch) | |
tree | 98fe48041dd58816aee5d6183d61100df68de4c4 /drivers/leds/trigger/ledtrig-oneshot.c | |
parent | c6084cbce435fbf800f47026896137b3bae483c3 (diff) | |
download | linux-9055082fb100cc66e20c048251d05159f5f2cfba.tar.xz |
scsi: add Synology to 1024 sector blacklist
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.
I have posted this a long while back, but it was not merged. This
version just fixes it up for merge/patch failures in the original
version.
Reported-by: Ancoron Luciferis <ancoron.luciferis@googlemail.com>
Reported-by: Michael Meyers <steltek@tcnnet.com>
Signed-off-by: Mike Christie <mchristi@redhat.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Cc: <stable@vger.kernel.org> # 4.1+
Diffstat (limited to 'drivers/leds/trigger/ledtrig-oneshot.c')
0 files changed, 0 insertions, 0 deletions