From f9182e3b007da9c1929e035938920b4003f02235 Mon Sep 17 00:00:00 2001 From: Vladislav Bolkhovitin Date: Fri, 25 Sep 2009 19:39:25 +0000 Subject: [PATCH] Not completed documenting how to workaround Windows READ CAPACITY(16) bug completed git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@1147 d57e44dd-8a1f-0410-8b47-8ef2f437770f --- scst/README | 4 ++-- scst/README_in-tree | 8 ++++++++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/scst/README b/scst/README index 6e6adb685..be3bd5c82 100644 --- a/scst/README +++ b/scst/README @@ -167,8 +167,8 @@ IMPORTANT: Some versions of Windows have a bug, which makes them consider As the result, such Windows'es refuse to see SCST exported devices >2TB in size. This is fixed by MS in latter Windows versions, probably, by some hotfix. But if you're using such - buggy Windows and experience this problem, change this '1' to - '0'. + buggy Windows and experience this problem, change in + scst_vdisk.c::vdisk_exec_read_capacity16() "#if 1" to "#if 0". To uninstall, type 'make scst_uninstall'. diff --git a/scst/README_in-tree b/scst/README_in-tree index 7029d25cc..00fae1764 100644 --- a/scst/README_in-tree +++ b/scst/README_in-tree @@ -85,6 +85,14 @@ IMPORTANT: In the current version simultaneous access to local SCSI devices devices READ/WRITE commands using direct disk handler look to be safe. +IMPORTANT: Some versions of Windows have a bug, which makes them consider +========= response of READ CAPACITY(16) longer than 12 bytes as a faulty one. + As the result, such Windows'es refuse to see SCST exported + devices >2TB in size. This is fixed by MS in latter Windows + versions, probably, by some hotfix. But if you're using such + buggy Windows and experience this problem, change in + scst_vdisk.c::vdisk_exec_read_capacity16() "#if 1" to "#if 0". + Usage in failover mode ----------------------