Allow OneDrive folder to be on a Storage Space (ReFS File System)
With OneDrive storage allowances greatly increasing, I would like to be able to move my local OneDrive folder into my Storage Space. My primary hard drive is an SSD with limited space. Currently, OneDrive folders are limited to NTFS formatted drives/partitions.
Thanks for the suggestion. Please take a look at this update: https://support.microsoft.com/en-us/help/4034825/features-that-are-removed-or-deprecated-in-windows-10-fall-creators-up
Braden Dodge commented
So basically Microsoft's answer to professionals is "our software is no longer being made with professionals in mind. If you want to be a professional you should use something else." Ok, good luck with that, more and more enterprises are getting fed up with your heavy handed "we know what's best for you" BS. Why are you guys even pursuing reFS (it's one of your selling points for Pro for Workstations for god's sake!) when you aren't bothering to support in on one of your flagship platforms??? You guys are a ******* mess and I'm not laughing. I'm mad as ****.
I don't think this is what Satya had in mind when using the word "disruptive." Disrupt the competitors, not the customers please!
In case it wasn't clear from my prior post, I literally erased a whole setup on NTFS just to reformat with ReFS on the same drives, so days of data transfers and OS upgrades and drive preparation and re-transferring the same data back onto the newly magic ReFS drives Microsoft documentation sold me on, all those hours of reading and planning and reading and planning and consulting support and reading and planning, then implementing ONLY TO DISCOVER THE FATAL FLAW IN MY WORK WHEN I GOT THE DIALOG BOX TELLING ME THAT I SHOULD GO TO JAIL, GO DIRECTLY TO JAIL, DO NOT PASS GO! Yah, it's a MONOPOLY reference. Ouch. I am stunned. Shocked. Gut-wrenched. I get it. I should have just bought MICROSOFT MANAGED DESKTOP. It's not available yet, so I tried to buy M365E5 instead, but it's not available without a partner in the middle, so I cobbled O365 E3, EMS E5, and upgraded local OS to Windows 10 Professional for Workstations solely to implement what Douglas says isn't available despite it's what I was sold through various documentations and sales literatures all over the Microsoft websites. Yah, I am sorely disappointed. The shock and outrage sprinkled among the comments on this topic are real, for sure. I hope adding this one USER's VOICE to the thread helps bring about a solution!!! The whole business model of create dependency, remove feature, repackage and create a subscription service for removed feature, reintroduce old feature as if it's a revolutionary new service once the subscription foundation is built is... painful.
No, Azure. Said in response to the post: "anonymous commented · July 2, 2017 11:20 PM · Flag as inappropriate
Why is MS kicking off users off Storage Space volumes when they been using them fine for years? Storage Space is a Windows component, so it's very strange. I guess MS is trying to push everyone to Amazon S3..."
I hope "right now" is nearer to November 2018 because... My OneDrive-CompanyName works on ReFS. I used the location property of Known Folders to move all the default save locations into all my user's OneDrive-Company Name. Since that feature started out in OneDrive-PersonalName, and the integration of the Sync Engine works the same for both, I "assumed" parity on being able to use ReFS to keep all my user's paths intact and make a transparent, undetectable change to ReFS under ALL MY USER'S OneDrive local folders. After all, It offers to "add account" just as before on NTFS. So I upgraded machines to the OS that allows creation of ReFS SOLEY TO GET ReFS, WHERE I INTENDED TO IMPLEMENT BOTH OneDrive-CompanyName and OneDrive-PersonalName for all my users with all the paths exactly as they were on NTFS before. Who knew this would be a problem while learning from Microsoft's storage documentation and videos all about how to configure Storage Spaces Direct / Storage Spaces to make the most of a mixture of smaller, expensive, faster drives alongside larger, more affordable, slower drives? Not me. Who knew this would be a roadblock when Microsoft has been extolling the superiority of ReFS as the successor to NTFS for several years now? Not me. I am working very hard to learn the best ways to implement Microsoft Products across my organization and seemingly really counterintuitive stumbling blocks abound, and this is a pretty big one for my user's consistency of work patterns. Too bad upvoting is closed on the issue, so "who knows" if there's demand for this out there?
I have not tested Ken's trick below and it is definitely simpler than mine:
A way to go around NTFS limitation is to create a VHDX filesystem image on ReFS formatted with NTFS and install Onedrive there. I have been running this setup more than a month and the system has proven to be stable and has survived few blue screens too. I have written detailed instructions to OneDrive Reddit: https://www.reddit.com/r/onedrive/comments/964bv7/how_to_use_onedrive_on_refs_and_circumvent/
BUT Please try Ken Flack's trick below first. It is far simpler.
This is just insanely bad decision by the OneDrive team. Why not to support ReFS, but without the "Files on Demand Feature"? I refunded my Win10 Pro for Workstations purchase just because of this.
Ken Flack commented
I moved the OneDrive folder to my ReFS volume (E:\OneDrive in my case) using these instructions. https://support.microsoft.com/en-au/instantanswers/346c0dc9-68fb-4189-9674-8011c670c3de/change-the-location-of-your-onedrive-folder
For me, C:\ is an NTFS volume that I use for booting Windows and running Apps.
I then used Command Prompt
Change directory to my user directory
Then used mklink to create a symbolic link
mklink /j OneDrive E:\OneDrive
symbolic link created for OneDrive <<===>> E:\OneDrive
I then proceeded to set up OneDrive pointing to C:\Users\chris (which is now symlinked to E:\OneDrive)
Hope that helps someone.
The admin answer actually has nothing to do with this issue anyways. That article is saying that only pro users can create an refs formatted space, the question is about not being able to put one drive on an existing refs space, or one drive stopping working on an refs space that it was already on. completely different.
Just lost 2 mirrored 4tb wd black disks 36 hours in a storage space among other 20tb of disks.. of course since I no longer have unlimited one drive, I don't have everything there as i've had to triage my 1tb of one drive regularly, and somehow, somehow this disk failure corrupted my 8tb image backup, and only have 3tb of file history.. In my 2 weeks of frantically cloning and recovering to a new refs storage space, bring it back up with a minimal amount of files that are inaccessible, now I have a new error, unsupported file system, move to ntfs... now what I need to buy another pair of mirrored drives and format as ntfs just to get my data moved again... So much for trying to go through and figure out which "found" folder files I need to find a way to restore, now I'm wasting more time... Between one drive and Bitcasa I have been fighting with idiotic cloud services more than using my data. Microsoft you sure know how to make one drive useless once again.
This is ridiculous answer. Win10 team created a new high-end SKU "Win 10 Pro for Workstations" and moved ReFS support there. Onedrive team puts mines on the Win10 team's plans by dropping ReFS support on Onedrive. Why you need competitors when you have colleagues like this, LOL. Great team spirit, Onedrive team!
I suspect ReFS support was dropped since the new OneDrive introduced "Files on-demand" feature relying on some low-level NTFS features. But why would I need "Files on demand" on PC? Smallest hard drives are 1 TB and above. I get the laptop use case, but do not forget your PC/workstation users. I specifically disabled the "Files on-demand" feature right after the update. For me ReFS and its data checksums are far more important than "Files on-demand".
It is also architecture-wise a wrong call to lock oneself into single filesystem. NTFS is 30 years old filesystem and simply outdated (vs. ZFS, BTRFS) ...
James Hancock commented
What a stupid answer. Onedrive MUST support ReFS. DUH.
@Douglas Pearce, what is the point of user voice, if you are providing comments that lack relevant info?
That sounds arrogant, because you just rejected the uservoice, without ever addressing the question of why it was removed in the first place?
The response of "Not Right Now" is incorrect. Would be better if it was "Why Right Now" (removing ReFS support that already existed).
Erick Sodhi commented
You're kidding me. My visceral reaction is WTF are you doing, Microsoft. The OneDrive client is an abominations, being an abysmally poor performer with a large number of synced files, and now no support for ReFS. This is farcical. I'm using an ReFS-formatted Storage Space pool and now have to figure out how to rejig my environment, not to mention finding the time to move a few TB of data around. Douglas, the link you provided to the deprecated features in the Fall Creators Update does NOT address the issue of OneDrive not supporting ReFS. Why do OneDrive for Business and SharePoint Team sites still work but personal sites not? Is support being removed completely for ReFS?
Janne Granström commented
fileserver with onedrive-d, sync all the files your fileserver and use them there :)
I too pay for Office 365, and use Microsoft Products, which is why I created a file store using the REFS files system. With the new Windows 10 Pro workstation patch approaching, the default file system is REFS.. Do you not plan to address this issue? Can you not issue an official statement regarding this feature? I also hold Microsoft stock, as a previous employee. Why would you make a move like this? It's user hostile and you did so without even telling us. Fix it.
Mathew Wicks commented
In a related issue, we need support for "P" attribute files, (Reparse Points). Because they currently glitch up on the Windows 10 OneDrive, and fail to upload.
Ken Flack commented
Considering I specifically purchased Office 365 to perform on-line backups (1 TB) MS really messed up. Its one thing not to offer a service, but to sell it to you, and then remove it without offering a refund is "illegal". Should be a class action suit for this one.
I downloaded a synchronization program called Good Sync that does the same task, and actually has more options available for setting up sync, and works with REFS
You can find it here at this link.
They offer 30 days free use,and also support syncing with many other on-line storage vendors. It works so well I bought a license for $20 (Discounted) and have signed up for their affiliate program. Trying to earn back the $ lost due to MS incompetence.
By removing exFAT support, Microsoft has broken compatibility with larger SDXC cards. The came cards Microsoft promoted as a solution to the Surface having limited storage space! AND THERE WAS NO WARNING OR COMMUNICATION FROM MICROSOFT!
Why did you remove functionality with exFAT file system? I had everything working fine on my tablet PC until you removed this. If technology is moving forward, why did you go backwards?!?! Please re-instate this feature ASAP. My only other option is an external hard drive via micro USB connection. In a world of improving technology, this option is very retro.