ReFS and Storage Spaces: Desired features exist in new version?


hey all,

windows 2012 brought refs , storage spaces, 2 nice technologies quite variety of restrictions.

then 2012 r2 added alternate data streams things sql server housed on file system , still run dbcc.

now windows server 2015 in pipeline there few outstanding quality of life , usability issues need addressed these 2 technologies , haven't seen commenting on these features are:

1) storage spaces parity block re-leveling.
when add new set of disks storage space, there tool or power shell switch allow spread parity blocks original disks in set, 5 disks in parity space, newly added 5 disks storage space parity data spread amongst disks in space? expanding storage spaces shouldn't hard, please make life easier. :)

2) useful features compression , quotas coming refs in version of windows?
when using ssds journaling , writeback cache parity spaces, performance more suitable common user file shares limited features available file system including quota , compression features of ntfs. these features making return in 2015? please yes, i'd able sell cheap commodity full featured small business servers people need lot of reliable storage without hassle of paying netapp or emc enormous sums privilege. market there microsoft, feel free jump in.

3) enterprise people amongst see things fcoe support iscsi targets on 2015, or did have mental blow out , there? being able provide full spectrum of smb , nfs along solid block level raw storage on ethernet super. :d

thanks in advance if yeses three. :)

refs not support compression (...and deduplication) in windows server 10.

there's no fcoe target in windows server 10 either...


starwind virtual san clusters hyper-v without sas, fibre channel, smb 3.0 or iscsi, uses ethernet mirror internally mounted sata disks between hosts.



Windows Server  >  Windows Server Technical Preview



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607