refs
7 TopicsReFS volume appears RAW (version doesn't match expected value) after Windows Update
After Windows Update last night, Windows Server 2019 wouldn't mount a storage space volume as ReFS (it appears as RAW). The error in the ReFS event log is "ReFS failed to mount the volume. Version 1.2 doesn't match expected value 3.4" No issues that I can see at the storage space level (it is a mirrored disk). The volume was working fine before Windows Update and the reboot. Another ReFS volume still works fine after the update. Any clues? I could not find this error mentioned anywhere else. Thanks.Solved131KViews3likes87CommentsCRITICAL - Storage Spaces: ReFS mirrored storage space will not free up space, related Defrag issues
This is an issue introed in the build of Windows 10 1903, first reported 8 months before release. I didn't thought this would be included in to Server 2022 LTSC since I have successfully worked on this to be fixed by the storage team in a Windows 10 Dev build. I have a running SR with MS support for over 1 year now so the fix from Insider dev gets at least backported to 2004 and later. They declined to fix it for 1903, 1909 due to end of support policies. Now this also affects an Server LTSC build for the first time it gets even more "spicy". Due a recent change of my Storage Space I had to "evacuate" all data from the Storage Space and found the same behaviour: issue: - deletion of files on the volume does not free up space (only ReFS mirrored volumes on Storage Spaced (not necessarily S2D, S2D was not tested). The space is shown as used on the Windows Explorer - deletion of files on the volume does not free up space on the Storage Pool affected OS: Windows 10 Pro / Enterprise / EDU 1903, 1909, 2004, 20H1, 20H2, 21H1 (beta channel), Windows Server SAC 1903 or later Windows Server LTSC 2022 LTSC (21H2) open SR: 120072921001646 this is not a local issue and can Feedback Hub (Storage Spaces file deletion issue): https://aka.ms/AAbfubr edit: (possibly related Defrag issues with Storage Spaces) https://aka.ms/AAbmte3Solved6.7KViews2likes11CommentsDirect Mode didn’t work on ReFS formated Cluster Shared Volumes
Hi, why is direct access not possible with a ReFS format CSV volume? Instead of direct access, all reFS formatted CSVs that are provided by a SAN runs with "FileSystemRedirected". This behavior is critical because the "FileSystem Redirected" mode, compared to direct access, has up to 90% or more performance losses depending on the environment. Neither the fact that ReFS formatted CSV only run in "FileSystem Redirected" mode nor the associated performance penalties are mentioned in any official Microsoft statement. On the contrary, Microsoft actively recommends using ReFS for VHDX files. That is why, like many others, I have formatted the CSV with ReFS since the server in 2016, because I hoped that this would be an advantage for the customer systems. Unfortunately, this procedure led to the opposite and it was not easy to find the reason for it. Mainly because Microsoft has absolutely nothing documented about this behavior. I personally had to postpone more than 100 TB of data on various customer systems over the past few months in order to eliminate this problem and to bring the CSV formatted with ReFS back to NTFS. This action cost my company a considerable amount and also led to massive annoyance of the customer. However, if you know what to look for, you can now find a lot of posts on the Internet that confirm this behavior. Here are a few examples. https://github.com/MicrosoftDocs/windowsserverdocs/issues/2051 https://www.hyper-v-server.de/hypervisor/performance-probleme-hyper-v-cluster-mit-san-storage-und-csvs-mit-refs-formatiert/ https://techcommunity.microsoft.com/t5/failover-clustering/understanding-the-state-of-your-cluster-shared-volumes/ba-p/371889 https://www.windowspro.de/marcel-kueppers/refs-ntfs-vor-nachteile-dateisysteme-server-2016 https://www.wowrack.com/blog/microsofts-latest-system-refs-compared-to-ntfs/ https://4sysops.com/archives/windows-server-2019-cluster-shared-volumes-best-practices/ https://social.technet.microsoft.com/Forums/ie/en-US/6b2dcc4f-e735-4700-81f3-df45d94e7e01/refs-for-a-hyperv-csv-volume?forum=winserverhyperv https://forums.veeam.com/veeam-backup-replication-f2/latest-veeam-community-forums-digest-oct-2-oct-8-t46019.html Therefore, I now spare myself any further details and come directly to my demand. If ReFS does not fundamentally support direct mode, then I also expect Microsoft to publicly clarify it accordingly and also clearly indicate which disadvantages could arise if the CSVs are formatted with ReFS. If it should work and there is only a bug in between, please finally fix it. This problem has existed since Server 2016, so enough time should have passed to fix the problem. Best Regards from Germany Alex1.9KViews1like0Comments