It occurs in versions 18 and 16, didn't try older ones. Parity drive is 980GB. The drive (J) causing the issue is 931GB with 1.39GB free.
First I tried a create the snapshot with it included with the 11 other drives, and it failed saying that 1.24TB where required for the update.
I removed the J drive from the configuration and the create completed successfully. I added the J drive back in and did an update and it failed saying it needed an additional 484.74GB to complete the update.
Any ideas?
Very strange indeed. DisParity determines the size needed by adding up the sizes of all the individual files to be added (it doesn't look at the size of the data drive itself.) So, that makes me think that perhaps there is a file on the J: Drive that is reporting a wildly innaccurate size for itself, which is throwing off the whole calculation. Offhand I don't know how that could happen, short of corruption of the MFT.
What sort of data is on the J: drive? Anything unusual? Lots of small files or fewer big files? Is it possible to glance through all the folders by hand and look for any file sizes that seem way off?
On the successful create (without the J:) drive, what did disParity report for the space available on the parity drive?
Turns out I had a junction in one of the folders, and it was delving into that and finding more data on another drive. Update running now. Thanks!
Alright, good to know in case this comes up again!
You must log in to post.