![]() As most of the software was never tested to support anything except 512 byte/sector. But! 1) It simply does not have any sense as non-standard sector size does no good to anybody - no performance increase as OS reads and writes with much larger blocks (multiple sectors per single request, 64KB in pre Windows 2003 times and 128KB-256KB in Windows 2008 and Vista storage stacks) 2) It's begging for troubles (exactly what you have). We can do 4096 (any size actually.) NOW, we could do it in 2003 as it's just different sector size reported in one SCSI command "read capacity". You may have 32KB sector (actually it's called "ECC block") on DVD+RW random-access formatted media on the host keeping StarWind IMG and say 8KB or 16KB or 512 byte/sector hard disk on the initiator-connected side. So sector size on the host has NOTHING to do with what we represent to the end user. We place container (flat image, CDP engine file set, TP sparse file etc) on the host file system (RAW, NTFS, FAT, EXT 2/3 etc - does not matter, it's up to OS, we rely on the file system driver here) and do EMULATE SCSI-3 compatible hard disk over iSCSI interface. StarWind is STORAGE VIRTUALIZATION software. StarWind Virtual Tape Library (VTL) OEM.StarWind Virtual Tape Library Appliance (VTLA).StarWind HyperConverged Appliance (HCA).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |