Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 31, 2019 4:08 AM
Hello,
I have been figurative banging my head against my desk trying to figure this out to not much avail. I have a storage space that I recently had to replace a drive on. The drive has been successfully replaced but now I have an odd lingering issue. My storage pool is currently at 13.6 TB (5x3TB drives) but my storage space for that pool is 15.9 TB. Every time i try and adjust the number down to 13.6 TB I get an error that says "the specified size is not valid". I really don't want an over allocated storage space but for some reason i cannot change it to match the pool size. Anyone have any ideas on what to try to fix it outside of deleting the 10TB of data on the drives and creating a new pool?
Thanks!
Josh
All replies (4)
Saturday, February 2, 2019 8:23 AM ✅Answered
Hi,
Thanks for your question.
I made a testing in my lab, we could extend the storage space with a larger size as 15.9TB in your environment. However, if we've already extended, we can't shrink to be lower down than this size, it will get the error "the specified size is not valid" as below.
Based on my experience, this is a design behavior. Now although this storage space size changed to a larger size for the purpose that we can add more drives to it. But available size of the space we can store the data is always based on value of the attributes "Available pool capacity".
The reference talked about a similar issue for you, hope this helps.
If you have any question or concern, please feel free to let me know.
Best regards,
Michael
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Thursday, January 31, 2019 4:44 AM
Hi Josh,
Have a look at this thread
Hope this helps!
Please don't forget to “mark the replies as answers” if they helped, also set "like" it’s a boost for us to keep blogging J
Click here to learn more. Visit the dedicated Community forum to share, explore and talk to experts about Microsoft Kaizala.
Thursday, January 31, 2019 5:53 AM
Yeah, I saw this one, but I wasn't sure it applied since I only had 13.6 TB of storage space and not more than 16TB. I was trying to reduce the 15.9 TB that is currently assigned down to 13.6 TB and not above 16 TB.
Sunday, February 3, 2019 12:22 AM
I ended up just shrinking the volume in Disk Management to get the desired effect. I was running into issues because the drive would keep filling up past the 13.6 TB because it said it had 15.9 TB of space to write to.