November 29, 20241 yr Hello, Been looking at about 20 of these kinds of threads from here and on Reddit, and none of them seem have been really helpful for me so far. My array is as follows: Should be plenty of space on each individual disk, the array, and the cache pool. My share settings (on the only share I've made myself) are like so: Here's the Windows error message: And how much space the files I'm trying to put on there are taking: I did get SOME files onto the share: The reason there are so many folders is because I initially tried using FreeFileSync to move stuff over, that one failed on other stuff. So it'd seem like it's being treated as a roughly ~125GB space. All the other threads I saw about this seemed to either be much closer to full, or had the minimum free space set to a teeny tiny value, but neither of these is true here. There should be plenty of space everywhere, and the minimum free space is around 6x the data being transferred, let alone the individual files (largest I can see is 26GB). Any clue as to what's going on?
November 29, 20241 yr Community Expert Reduce that on each share to something more reasonable like twice the size of the biggest file you expect to transfer to the share, 100GB probably a good starting point.
November 29, 20241 yr Author 2 minutes ago, Kilrah said: Reduce that on each share to something more reasonable like twice the size of the biggest file you expect to transfer to the share, 100GB probably a good starting point. Went with 146GB, about 2x the size of the biggest file I have on the old device I'm trying to evacuate. Set that, hit apply, still getting the same error when I try to transfer.
November 29, 20241 yr Community Expert Try it without the share being 'hidden'. (I seem to recall that there have been other users with issues when using hidden shares.)
November 29, 20241 yr Author 5 hours ago, Frank1940 said: Try it without the share being 'hidden'. (I seem to recall that there have been other users with issues when using hidden shares.) Gave it a bash, set to just Yes and hit apply, no change. 4 hours ago, JorgeB said: What's the share name? The one that's acting up is Perus-Share. I did actually make a new share called Test01, which has the exact same settings, and that one seems to be working just fine... WEIRD. EDIT: Interestingly the first share that's acting up is also not showing up as protected in the shares view, but the newer one is... Edited November 29, 20241 yr by jubuttib
November 30, 20241 yr Community Expert Pesus-Share has files on cache, that should not make a different for this issue, but move them to the array and retest.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.