Storage Spaces: Virtual Disk taken offline during file copy, marked as "This disk is offline because it is out of capacity", but plenty of free space

Question

Server 2012 RC. I'm using Storage Spaces, with two virtual disks across 23 underlying physical disks.
* First virtual disk is fixed provisioning, parity across 23 physical disks: 10,024GB capacity
* Second virtual disk is fixed provisioning, parity across the remaining space on 6 of the same physical disks: 652GB capacity
These have been configured as dynamic disks, with an NTFS volume spanned across the two (larger virtual disk first). Total volume size 10,676GB. For more details of the hardware, and why the configuration is like this, see: http://social.technet.microsoft.com/Forums/en-US/winserver8gen/thread/c35ff156-01a8-456a-9190-04c7bcfc048e
I'm copying several TB from a network share to this volume. It is very slow at ~12MB/sec, but works. However, three times so far, several hours in to the file copy and with plenty of free space remaining, the 10,024GB virtual disk is suddenly taken offline.
This obviously then fails the spanned volume and stops the file copy.
The second time, I took screenshots, below. The disk (Disk27) is marked offline due to "This disk is offline because it is out of capacity". And the disk in the spanned volume is marked as missing (which is what you would expect when one of its member disks
is offline).
I can then mark the disk (Disk27) back online again, and this restores the spanned volume. I can then re-start the file copy from where it failed. There doesn't appear to be any data loss, but it does cause an outage that requires manual attention. As you
can see, there is plenty of space left on the spanned volume.
Each time this has happened, there are a few event 150 errors in the System event log: "Disk 27 has reached a logical block provisioning permanent resource exhaustion condition.". Source: Disk.
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="disk" /> 
  <EventID Qualifiers="49156">150</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2012-06-07T11:24:53.572101500Z" /> 
  <EventRecordID>14476</EventRecordID> 
  <Channel>System</Channel> 
  <Computer>Trounce-Server2.trounce.corp</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>\Device\Harddisk27\DR27</Data> 
  <Data>27</Data> 
  <Binary>000000000200300000000000960004C0000000000000000000000000000000000000000000000000</Binary> 
  </EventData>
  </Event>
This error seems to be related to thin provisioning of disks. I found this:
http://msdn.microsoft.com/en-us/library/windows/desktop/hh848068(v=vs.85).aspx. But both these Virtual Disks are configured as Fixed, not Thin provisioning, so it shouldn't apply.
My thoughts: the virtual disk should not spuriously go offline during a file copy, even if it was out of space. And in any case, there is plenty of free space remaining. Also, I don't understand the reason for why it is marked as offline ("This disk is offline
because it is out of capacity"). Why would a disk go offline because it was out of thin capacity, rather than just returning an "out of disk space" error while keeping it online.

Answer 1

Interesting Thread, I've been having the same issue. I had a failed hardware RAID that was impossible to recover in place, so after being forced to do a 1:1 backup, I find myself with 5 2TB hard drives to play with. Storage Spaces seemed like an interesting
way to go until I started facing the issues we share.
So my configuration is A VM Running Windows Server 2012 RC with 5 Virtualized Physical drives using a SCSI interface, 2TB in size that make up my storage pool. A Single Thinly provisioned Disk of 18 TB (using 1 disk for parity)
Interestly enough, write speed has not been an issue on this machine (30~70MB/s, up from 256k on the beta) 
Of note to me is this error in my event log 13 minutes before the drive disappeared:
"The shadow copies of volume E: were deleted because the shadow copy storage could not grow in time.Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."Source: volsnap, Event ID: 25, Level: Error
followed by:
"The system failed to flush data to the transaction log. Corruption may occur in VolumeId: E:, DeviceName: \Device\HarddiskVolume17.(The physical resources of  this disk have been exhausted.)"Source: Ntfs (Microsoft-Windows-Ntfs), Event ID: 140, Level: Warning
I figure the amount of space available to me before I start encountering physical limits is in the vicinity of about 7TB. It dropped out for the second time at 184 GB.
FYI, the number of columns created for me is 5
Regards,
Steven Blom