Storage Space bug report: Write bug (evt id 153)on reaching the actual capacity threshold (of the storage pool) for thinly provisioned drives in a parity setup.
This may be a problem in other cases as well i.e. a mirror setup.
I like Storage Spaces - but is has to work completely with the basic operations. Is it just a prototype - and not for real? Really, why aren't the issues with basic problems given priority in patch roll out? Just a toy ...? Or to be taken serious?
Symptoms: During a move file(s) operation from src a to dest b (thinly provisioned) a guest VM Windows 2012 R2 may report an evt id 153:The IO operation at logical block address ec80 for Disk 7 (PDO name: \Device\00000041) was retried
Problem: Data loss. The write operations retries - and if the user retires - the files will be moved - but be invalid. It has also been observed that some files where moved without user interaction - i.e. the automated retries where files are moved - but invalid at the destination - followed by a delete operation at the source. I.e. the move file transaction is commited with invalid data at the end.
Cause: ? So the bug here is the file operation is commited when the transaction did actually not complete - because of the evt 153 where pool was out of space?
Solution: Have seen so unrealibility over time since using storage spaces for more than a year now. Especially when creating storage Spaces on the host and giving those virtual disk to VM's as disk pass-through. I.e. the thinly provisioned drives may misbehave in context with optimize-volume and capacity issues. So this is just another symptom proofing Theres is a problem with thinly provisioned disk on the host and using them with VM's. Should be fixed asap to increase realibility.
A temporary solution - maintaining the use of storage spaces - is to move the disk out of the VM and back to the host environment where the provisioning always seem to work correctly and use i.e. file shares.
Untill now I could "live" with thinly provisiioned drived in VM's having a problem with volume-optimization still waiting for Microsoft to fix it. However, I do not prefer the risk of data loss. So will move those disk out of VM's.
So essentially the Host is now the file server ...
If not fixed, will try out Linux as the file server ... as I have also been waiting for more effective use of checksums (like in ReFS) coupled with more flexibility like in attributes of NTFS.
I like Storage Space - but is has to work. Is it just a prototype - and not for real?