From: Michel Meyers <steltek@tcnnet.com>
To: linux-scsi@vger.kernel.org
Cc: Mike Christie <mchristi@redhat.com>
Subject: [PATCH 1/1] scsi: add Synology DSM 6.0 and higher to 1024 sector blacklist
Date: Mon, 11 Apr 2016 10:43:36 +0200 [thread overview]
Message-ID: <570B63B8.6080104@tcnnet.com> (raw)
In-Reply-To: <20160114003437.354D28EE1D4@bedivere.hansenpartnership.com>
From: Michel Meyers <steltek@tcnnet.com>
SYNOLOGY iSCSI devices do not work with large I/O and SYNOLOGY changed
the identifier of the devices starting with version 6.0 of their OS
("DSM"). (The large I/O problem persists in that release.)
This patch adds the new identifier to the 1024 sector blacklist, the old
one having been added in commit 9055082fb100cc66e20c048251d05159f5f2cfba
"scsi: add Synology to 1024 sector blacklist".
Reported-by: Michel Meyers <steltek@tcnnet.com>
Signed-off-by: Michel Meyers <steltek@tcnnet.com>
---
diff --git a/drivers/scsi/scsi_devinfo.c b/drivers/scsi/scsi_devinfo.c
index 3408578..46b5e2e 100644
--- a/drivers/scsi/scsi_devinfo.c
+++ b/drivers/scsi/scsi_devinfo.c
@@ -232,6 +232,7 @@ static struct {
{"Promise", "", NULL, BLIST_SPARSELUN},
{"QNAP", "iSCSI Storage", NULL, BLIST_MAX_1024},
{"SYNOLOGY", "iSCSI Storage", NULL, BLIST_MAX_1024},
+ {"SYNOLOGY", "IBLOCK", NULL, BLIST_MAX_1024},
{"QUANTUM", "XP34301", "1071", BLIST_NOTQ},
{"REGAL", "CDC-4X", NULL, BLIST_MAX5LUN | BLIST_SINGLELUN},
{"SanDisk", "ImageMate CF-SD1", NULL, BLIST_FORCELUN},
next parent reply other threads:[~2016-04-11 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160114003437.354D28EE1D4@bedivere.hansenpartnership.com>
2016-04-11 8:43 ` Michel Meyers [this message]
2016-04-12 2:20 ` [PATCH 1/1] scsi: add Synology DSM 6.0 and higher to 1024 sector blacklist Martin K. Petersen
2016-04-12 8:28 ` Michel Meyers
2016-04-12 18:42 ` Martin K. Petersen
2016-04-12 19:18 ` Mike Christie
2016-04-12 19:22 ` Martin K. Petersen
2016-04-20 8:46 ` Michel Meyers
2016-04-26 2:12 ` Martin K. Petersen
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=570B63B8.6080104@tcnnet.com \
--to=steltek@tcnnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.