i dont know if it is a bug, or if i missed something.
i have an iscsi target mounted by an MS hyper-v server as a raw disk
on that disk sits a windows 2008 r2
my iscsi logical block size is 512
after upgrading from 9.2.1.8 to 9.3 the disk reports physical sector size 131072 (i think it was 4096 before but not sure).
fsutil fsinfo ntfsinfo c:
windows runs, but has several problems.
for example:
esentutl /g %windir%\security\Database\secedit.sdb
also an mssql database is no longer able to start, because the master table was created for 4096 bytes sector.
i have an iscsi target mounted by an MS hyper-v server as a raw disk
on that disk sits a windows 2008 r2
my iscsi logical block size is 512
after upgrading from 9.2.1.8 to 9.3 the disk reports physical sector size 131072 (i think it was 4096 before but not sure).
fsutil fsinfo ntfsinfo c:
Version : 3.1
Bytes per sector : 512
Bytes per physischen sector : 131072
Bytes per Cluster : 4096
Bytes per filedatasegment : 1024
Cluster per filedatasegment : 0
windows runs, but has several problems.
for example:
esentutl /g %windir%\security\Database\secedit.sdb
Extensible Storage Engine Utilities for Microsoft(R) Windows(R) Version 6.1
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating INTEGRITY mode...
Database: C:\Windows\security\Database\secedit.sdb
Temp. Database: TEMPINTEG5256.EDB
Operation terminated with error -583 (JET_errSectorSizeNotSupported, The physical sector size reported by the disk subsystem, is unsupported by ESE for a specific file type.)
also an mssql database is no longer able to start, because the master table was created for 4096 bytes sector.
Last edited: