On 2016-04-12 21:22, Martin K. Petersen wrote: >>>>>> "Mike" == Mike Christie <mchristi@xxxxxxxxxx> writes: > >>> Mike: Any preference? > > Mike> I think quirking SYNOLOGY is best. It will be the safest route and > Mike> work for all devices. > > Michel: Please spin a new version of the patch. Apologies for not getting back earlier. SYNOLOGY have released a new version of their OS indicating that they have worked to fix the iSCSI problem (and another one to actually make that update installable): https://www.synology.com/en-global/releaseNote/RS10613xs+ - "Fixed multiple issues that might cause iSCSI service to hang under heavy loading and performing Vmware VAAI commands." - "Fixed an issue where DSM 6.0-7321 Update 1 could not be normally installed with Auto-Update." (They have not updated my support ticket on this case thus far.) Both my SYNOLOGY appliances now seem to show correct vpd data when queried: root@server:/# sg_vpd -p bl /dev/sdb Block limits VPD page (SBC): Write same non-zero (WSNZ): 1 Maximum compare and write length: 1 blocks Optimal transfer length granularity: 128 blocks Maximum transfer length: 8192 blocks Optimal transfer length: 1152 blocks Maximum prefetch length: 0 blocks root@server:/# sg_vpd -p bl /dev/sdd Block limits VPD page (SBC): Write same non-zero (WSNZ): 1 Maximum compare and write length: 1 blocks Optimal transfer length granularity: 128 blocks Maximum transfer length: 8192 blocks Optimal transfer length: 512 blocks Maximum prefetch length: 0 blocks I am currently running tests with an unmodified Debian 4.4.0-1-amd64 kernel, so unless I can reproduce the problem, I suggest we leave the current blacklist as is (thereby only quirking the pre-6.0 SYNOLOGY volumes that are affected) and discard the new patch. -- Michel -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
