Leaderboard

I'm using Windows Server 2016 Datacenter (GUI Version - newest updates) on a dual socket system in combination with CloudDrive (newest version). The only problem I had, was to connect with the Internet Explorer to the cloud service. Using a 3rd party browser solved this. But I'm always using ReFS instead of NTFS...

Even more useful now. I have all my data more or less duplicated on gdrive. As my penchant for higher quality files grows local space becomes more of an issue (but not in anyway terminal). As a result some shows that friends/family have asked for and not to my personal taste reside solely on gdrive (which has a separate Plex Server attached to it). I tried NetDrive @ Drive File Stream for a while, pointing my local server to those. This lead to one of two evils. All the shows I have locally would show as duplicates OR in Plex I would have to point to the individual show directories for stuff that is only on google (far too lazy to separate the shows on google itself). On a whim I just decided to see what would happen if i selected some show folders on Drive File Stream and make directories junctions for them. I really didn't expect it to work and yet it did. I went to my google api screen to monitor the hits while Plex scanned the files in and everything was fine. So now I'm gonna set up a separate folder consisting only of these junction points and point Plex to that. If I do ever get around to watching these shows they are there without switching to the Gdrive mounted server or having to download terrabytes of data locally for shows I may never bother with. I have no idea about Directory Junctions inner workings... but wow this is game changing for me.

Yep. I'm not really a command line type of guy. But http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html this really helped.

What's fantastic is that DrivePool supports them!

That’s exactly what I see too with Google drives – frequent “pinning data” phases with extreme CPU loads. Unclear, why pinning needs to be performed at all. Neither directories nor metadata are being changed on any drive. One drive is only downloading (being scanned for Crashplan backup). The pinned data volume suddenly gets reduced by a certain amount (e.g. 200 MB), what then triggers such a pinning phase and lets the entire system freeze almost completely for a couple of minutes – that happens multiple times a day.

Is this for video editing? If so, you might want to consider larger SSDs for the cache, or using a non-pooled SSD for editing purposes and moving the files when you're done (the file you are creating - the source material will be fine left on the pool as you're only reading).

Good points, I think I have my answers now. I did some more reading as well and I have enabled file integrity on each of my drives within my pool. Any drives I add from now on out I will format with file integrity enabled from the start. Thanks for the walk through!! Best wishes, Scott

If that's the case, then yeah, it definitely sounds like it was a timing issue.

I should do this with my VM lab... But no, I've never had the opportunity to set this up.

You're very welcome, and I'll let you know as soon as I have feedback from Alex.

You're very welcome for it! And yeah, the larger chunk size means potentially lower overhead, so it's not a bad idea, if this is for multimedia storage.

Wow, that issue sure shows up a lot in the service log. I've flagged the logs for Alex (the Developer), so he can check. https://stablebit.com/Admin/IssueAnalysis/27781

Larger chunk sizes is a good idea. But aside from that, the defaults should be pretty good, actually. And the 63TB thing ... the drive can be larger than that. But if it is, you'd want to partition the drive so that no single partition is larger than that.

I needed to go into Disk Management and activate the drive on server 2008. Perhaps you will have to do the same.

The box for the capacity is a text box. You can type on any value you want (that ... is supported, at least, so up to 1PB). As long as your provider has the free space for it. Just remember that the largest cluster (allocation unit) size may be 64kb on most versions of Windows, which means 256TB volume, max. Also, note that you may not want to have partitions/volumes that are larger than 63TBs, as Windows has issues with disk checking if the volume is NTFS and 64TBs or larger... You can partition and pool the partitions to avoid the issue, if needed... But ....

It's probably safe to ignore. Just in case, could you run the StableBit Troubleshooter on the system in question? http://wiki.covecube.com/StableBit_Troubleshooter Use "3525" as the Contact ID in the Troubleshooter.