• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Home Server

I don't think you are understanding what you are reading. The D parition on the system drive, the system drive itself should be your largest drive.
The rules you have posted for the data writes are what WHS to move data off of the D parition. They aren't for the D partition itself.

That data movement you are seeing is me doing a direct write to the server from another machine. Sigh...believe what you want.
 
That data movement you are seeing is me doing a direct write to the server from another machine. Sigh...believe what you want.

It's not a matter of me believing what I want. Your own link states just what I told you. And what your screenshot shows is also what we have said.

Your D partition is showing movement, it's receiving the data you are transferring over. The system then(following the rules you posted) has selected a drive and is transferring to it. Which is exactly what it should be doing based upon what I, coldzero and your link show it should be doing.
Data transferred over the network goes to the D parition on the system drive. WHS moves it off. The free space on the D partition is what is reported to the rest of your network. It can only receive as much data at a time as it has space. WHS makes a decision on which drive is to hold that data. PP1 certainly makes that happen faster now.

Perhaps there is merely a misunderstanding here, you're not understanding what we are saying or misinterpreting something. Ask people on the official forums if you don't believe me. You can copy and paste what I have said, they'll tell you.
 
What I said is still true.

PP1 only changed the balancing algorithm, you stil have a Landing Zone which is what is reported to computers when they look for the free space. The algorithm follows the rules in the link you posted, but the actual landing zone is still there and is where files are copied to in the first place before DE copies them to whatever drive they are going to.

There is actually a bug right now in PP1 where the landing zone doesn't get cleared out and you can't copy things to the server. There is also a tool called LZrelocator that will let you change the location of your landing zone to something other than the original. I haven't used it, but I guess it works.
 
I just checked over at "we got served" because I wanted to make sure (you were arguing strong enough). And what I said was correct...there is NO landing zone as it was once was with PP1. The file goes DIRECTLY to the drive it supposed to go to. This change was part of the fix for the corruption issue.

Therefore data that goes over the network may not go directly to D: The image I posted proves that (it is from my own server).

As for D:\ getting filled...it shouldn't. The last spot files go is D:\ Therefore the maximum transfer size should be kept large until your server is start to approach capacity. The thing I don't know (which I have now asked) is if the transfer algorithm looks at the group of files you select or the size of the maximum single file in PP1 with the current bug of only looking at D:\ (this is the bug that I am aware of).
 
I just checked over at "we got served" because I wanted to make sure (you were arguing strong enough). And what I said was correct...there is NO landing zone as it was once was with PP1. The file goes DIRECTLY to the drive it supposed to go to. This change was part of the fix for the corruption issue.

Therefore data that goes over the network may not go directly to D: The image I posted proves that (it is from my own server).

As for D:\ getting filled...it shouldn't. The last spot files go is D:\


That is correct
 
You realize that in the reply to your post on wegotserved:

Again, you're believe about how the migrator works *now* is correct, and you should stick to that. smile.gif The only thing is that vista is limited to how much free space is on the D:\ partition for copying files over at once.

is actually talking about the landing zone which files are then moved off of. You can see this easily by taking a screen shot of the free space on a share from a windows computer. It will be the size of your primary hard drive's data partition, not the sum of the drives.

Please read this thread at Microsoft's forums. While the balancing is different, the landing zone still exists and there is an actual bug that made it into PP1 that they knew about but did not hold the release for.
 
Back
Top