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
This commit is contained in:
Vladislav Bolkhovitin
2009-09-25 19:39:25 +00:00
parent 93e8178a4f
commit f9182e3b00
2 changed files with 10 additions and 2 deletions

View File

@@ -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'.

View File

@@ -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
----------------------