Windows 10 Pro 2004 - Removing a disk from fully mirrored Storage Pool is not possible - low space

%3CLINGO-SUB%20id%3D%22lingo-sub-1473949%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20%2F%20Server%20-%20Removing%20a%20disk%20from%20a%20Storage%20pool%20is%20not%20possible%20low%20space%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473949%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20now%20added%20a%202%20TB%20drive%20and%20the%20StorageJob%20are%20now%20running%2C%20but%20the%20base%20question%20is%20why%20this%20is%20neccessary%20technically%20in%20the%20first%20place.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1478336%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20%2F%20Server%20-%20Removing%20a%20disk%20from%20a%20Storage%20pool%20is%20not%20possible%20low%20space%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1478336%22%20slang%3D%22en-US%22%3EUltimately%20I%20had%20to%20supply%20drives%20of%20the%20same%20size%20of%20the%206TB%20drive%20I%20want%20to%20remove.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20added%20a%202%20TB%20internal%20and%203%20TB%20USB%203.0.%3CBR%20%2F%3E%3CBR%20%2F%3ESo%20basically%20the%20effective%20use%20of%20what%20I%20am%20going%20to%20remove.%3CBR%20%2F%3EThen%20I%20was%20able%20to%20remove%20the%20drive%20marked%20retired.%3CBR%20%2F%3E%3CBR%20%2F%3EStill%20question%20unanswered%20why%20one%20cannot%20remove%20a%20mirrored%20drive.%20If%20it%20was%20striped%20or%20distributed%20I%20would%20understand%20this%20behaviour.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1473936%22%20slang%3D%22en-US%22%3EWindows%2010%20Pro%202004%20-%20Removing%20a%20disk%20from%20fully%20mirrored%20Storage%20Pool%20is%20not%20possible%20-%20low%20space%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1473936%22%20slang%3D%22en-US%22%3E%3CP%3EScenario%3A%3CBR%20%2F%3EWindows%2010%202004%3CBR%20%2F%3E1%20Storage%20Pool%3CBR%20%2F%3EStorage%20Pool%20functional%20level%3A%20vServerNext%3CBR%20%2F%3E%3CBR%20%2F%3EPool%20consists%20of%202%20x%206TB%20same%20Harddisk%3CBR%20%2F%3E%3CBR%20%2F%3E2%20virtual%20Disks%20(DATA%2C%20BACKUPS)%3CBR%20%2F%3EThin%20provisioned%2C%20NTFS%2C%20Default%20Cluster%20size%3CBR%20%2F%3EThe%20pool%20usage%20was%204%2C81%20TB%20out%20of%2010%2C9%20TB%20(before%20adding%20a%203rd%20disk)%3CBR%20%2F%3EDisk%20usage%20was%20balanced%2043-44%2C1%25%3CBR%20%2F%3EDefrag%20Storage%20Space%20efficiency%20(slab%20consolidation)%20is%2098%25-99%25%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20I%20am%20trying%20to%20do%3A%3CBR%20%2F%3EI%20need%20to%20remove%20one%20disk%20for%20maintenance%3CBR%20%2F%3EAs%20the%20virtual%20disks%20are%20both%20mirrored%20I%20suspect%20this%20would%20be%20possible%2C%20but%20it%20is%20not.%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20I%20did%20so%20far%3A%3CBR%20%2F%3E%23save%20object%20of%20disk%3CBR%20%2F%3E%24PDtoRemove%20%3D%20Get-PhysicalDisk%20-serialnumber%20SerialNr%3CBR%20%2F%3E%3CBR%20%2F%3E%23set%20disk%20as%20retired%20for%20removal%3CBR%20%2F%3ESet-PhysicalDisk%20%24PDtoRemove%20-Usage%20Retired%3CBR%20%2F%3E%3CBR%20%2F%3E%23idenfity%20the%20used%20virtual%20disks%20for%20this%20physical%20disk%3CBR%20%2F%3EGet-PhysicalDisk%20%24PDtoRemove%20%7C%20Get-VirtualDisk%3CBR%20%2F%3E%3CBR%20%2F%3E%23prepare%20for%20drive%20removal%3CBR%20%2F%3ERepair-VirtualDisk%20-FriendlyName%20'Data'%3CBR%20%2F%3ERepair-VirtualDisk%20-FriendlyName%20'Backups'%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20troubles%20me%3A%3CBR%20%2F%3E%23check%20jobs%3CBR%20%2F%3EGet-StorageJob%3CBR%20%2F%3EShows%20both%20repair%20jobs%20as%20suspended.%20GUI%20shows%20-%20needs%20more%20disk%20space.%3CBR%20%2F%3E%3CBR%20%2F%3ERemoving%20the%20disk%20with%3CBR%20%2F%3ERemove-PhysicalDisk%20%24PDtoRemove%3CBR%20%2F%3E%3CBR%20%2F%3EOutput%3A%3CBR%20%2F%3E%26amp%3Bnbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E-%20Not%20enough%20available%20capacity%3CBR%20%2F%3EStorage%20pool%20dos%20not%20have%20sufficient%20capacity%20to%20relocate%20data%20from%20the%20specified%20disk%3CBR%20%2F%3E(remark%3A%20see%20Job%20suspended)%3CBR%20%2F%3Erecommended%20actions%3A%3CBR%20%2F%3E-%20add%20more%20physical%20disks%20to%20the%20storage%20pool%2C%20S%3CBR%20%2F%3E-%20free%20capacity%20by%20deleting%20unneeded%20virtual%20disk%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20leaves%20me%20alone%20if%20I%20understood%20the%20concept%20of%20Storage%20Spaces%20Mirror%2C%20is%20equivalent%20of%20RAID%201%2C%20where%20I%20could%20remove%20%2F%20fail%20one%20drive%20anytime.%20Even%20more%20here%20the%20capacity%20has%20not%20even%20reached%2050%25%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EWhat%20I%20expect%20to%20happen%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20a%20mirror%2C%20expect%20some%20metadata%20overhead%20for%20the%20pool%20and%20virtual%20volume%20this%20should%20not%20make%20a%20different%2C%20imho.%20It%20should%20tolerate%20this%20operation%20or%20a%20fail.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20don't%20want%20to%20imagine%20what%20happened%20if%20a%20drive%20really%20failed%20out%20of%20the%20blue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1473936%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage-Spaces%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Contributor

Scenario:
Windows 10 2004
1 Storage Pool
Storage Pool functional level: vServerNext

Pool consists of 2 x 6TB same Harddisk

2 virtual Disks (DATA, BACKUPS)
Thin provisioned, NTFS, Default Cluster size
The pool usage was 4,81 TB out of 10,9 TB (before adding a 3rd disk)
Disk usage was balanced 43-44,1%
Defrag Storage Space efficiency (slab consolidation) is 98%-99%

What I am trying to do:
I need to remove one disk for maintenance
As the virtual disks are both mirrored I suspect this would be possible, but it is not.

What I did so far:
#save object of disk
$PDtoRemove = Get-PhysicalDisk -serialnumber SerialNr

#set disk as retired for removal
Set-PhysicalDisk $PDtoRemove -Usage Retired

#idenfity the used virtual disks for this physical disk
Get-PhysicalDisk $PDtoRemove | Get-VirtualDisk

#prepare for drive removal
Repair-VirtualDisk -FriendlyName 'Data'
Repair-VirtualDisk -FriendlyName 'Backups'

What troubles me:
#check jobs
Get-StorageJob
Shows both repair jobs as suspended. GUI shows - needs more disk space.

Removing the disk with
Remove-PhysicalDisk $PDtoRemove

Output:
 

- Not enough available capacity
Storage pool dos not have sufficient capacity to relocate data from the specified disk
(remark: see Job suspended)
recommended actions:
- add more physical disks to the storage pool, S
- free capacity by deleting unneeded virtual disk

This leaves me alone if I understood the concept of Storage Spaces Mirror, is equivalent of RAID 1, where I could remove / fail one drive anytime. Even more here the capacity has not even reached 50%

What I expect to happen
For a mirror, expect some metadata overhead for the pool and virtual volume this should not make a different, imho. It should tolerate this operation or a fail.

I don't want to imagine what happened if a drive really failed out of the blue.

2 Replies
Highlighted

I have now added a 2 TB drive and the StorageJob are now running, but the base question is why this is neccessary technically in the first place. 

Highlighted
Ultimately I had to supply drives of the same size of the 6TB drive I want to remove.

I have added a 2 TB internal and 3 TB USB 3.0.

So basically the effective use of what I am going to remove.
Then I was able to remove the drive marked retired.

Still question unanswered why one cannot remove a mirrored drive. If it was striped or distributed I would understand this behaviour.