CopyOnWrite 0.3.7

The CopyOnWrite library provides a .NET layer on top of OS-specific logic that provides copy-on-write linking for files (a.k.a. CoW, file cloning, or reflinking). CoW linking provides the ability to copy a file without actually copying the original file's bytes from one disk location to another. The filesystem is in charge of ensuring that if the original file is modified or deleted, the CoW linked files remain unmodified by lazily copying the original file's bytes into each link. Unlike symlinks or hardlinks, writes to CoW links do not write through to the original file, as the filesystem breaks the link and copies in a lazy fashion. This enables scenarios like file caches where a single copy of a file held in a content-addressable or other store is safely linked to many locations in a filesystem with low I/O overhead.

NOTE: In the current package version only Windows functionality is implemented. Issues for Linux and Mac are open and contributions are welcome. Consider reimplementing from the Rust package linked below.

This library allows a .NET developer to:

• Discover whether CoW links are allowed between two filesystem paths,
• Discover whether CoW links are allowed for a directory tree based at a specific root directory,
• Create CoW links,
• Find filesystem CoW link limits.

Discovery is important, as different operating systems and different filesystems available for those operating systems provide varying levels of CoW link support:

• Windows: The default NTFS filesystem does NOT support CoW, but the ReFS filesystem and 2023's new Dev Drive do.
• Linux: Btrfs, Xfs, Zfs support CoW while ext4 does not.
• Mac: AppleFS supports CoW by default.

When using this library you may need to create a wrapper that copies the file if CoW is not available.

Example

using Microsoft.CopyOnWrite;

ICopyOnWriteFilesystem cow = CopyOnWriteFilesystemFactory.GetInstance();
bool canCloneInCurrentDirectory = cow.CopyOnWriteLinkSupportedInDirectoryTree(Environment.CurrentDirectory);
if (canCloneInCurrentDirectory)
{
    cow.CloneFile(existingFile, cowLinkFilePath);
}

OS-specific caveats

Windows

File clones on Windows do not actually allocate space on-drive for the clone. This has a good and a possibly bad implication:

• Good: You save space on-disk, as the clones only take up space for region clone metadata (small).
• Possibly bad: If cloned files are opened for append or random-access write, the lazy materialization of the original content into the opened file may result in disk out-of-space errors.

Release History

• 0.3.7 September 2023: Fix #30 - ignore ACCESS_DENIED on volume enumeration to avoid need to escalate privilege on Windows.
• 0.3.6 July 2023: Set AssemblyVersion to 0.9.9999.0 to allow mixing different minor-version binaries from different packages in the same appdomain/process.
• 0.3.5 July 2023: Set AssemblyVersion to 0.0.0.1 to allow mixing different minor-version binaries from different packages in the same appdomain/process.
• 0.3.4 July 2023: Handle locked BitLocker volume during volume scan.
• 0.3.3 July 2023: For Linux and Mac unimplemented filesystems, return false from CopyOnWriteLinkSupported... methods to avoid the need for checking for Windows OS before calling.
• 0.3.2 February 2023: Fix issue with ERROR_UNRECOGNIZED_VOLUME returned from some volumes causing an error on initialization on some machines.
• 0.3.1 February 2023: Fix issue with Windows drive information scanning hanging reading removable SD Card drives. Updated README with Windows clone behavior.
• 0.3.0 January 2023: Remove Windows serialization by path along with CloneFlags.NoSerializedCloning and the useCrossProcessLocksWhereApplicable flag to CopyOnWriteFilesystemFactory. The related concurrency bug in Windows was fixed in recent patches and retested on Windows 11.
• 0.2.2 January 2023: Fix mismatched sparseness when CloneFlags.DestinationMustMatchSourceSparseness was used (https://github.com/microsoft/CopyOnWrite/issues/17)
• 0.2.1 September 2022: Add detection for DOS SUBST drives as additional source of mappings.
• 0.2.0 September 2022: Improve documentation for ReFS parallel cloning bug workarounds. Improve Windows cloning performance by 7.2% by using sparse destination files. Default behavior change to leave destination file sparse and replaced CloneFlags.NoSparseFileCheck with DestinationMustMatchSourceSparseness, hence minor version increase.
• 0.1.13 September 2022: Fix CloneFlags to use individual bits.
• 0.1.12 September 2022: Add new factory flag that sets a mode to require cross-process Windows mutexes for safe source file locking to avoid a ReFS concurrency bug. Add optimization to allow bypassing redundant Path.GetFullPath() when caller has done it already.
• 0.1.11 September 2022: Serialize Windows cloning on source path to work around ReFS limitation in multithreaded cloning.
• 0.1.10 September 2022: Fix missing destination file failure detection.
• 0.1.9 September 2022: Add explicit cache invalidation call to interface. Update Windows implementation to detect ReFS mount points that are not drive roots, e.g. mounting D:\ (ReFS volume) under C:\ReFS.
• 0.1.8 April 2022: Add overload for CoW clone to allow bypassing some Windows filesystem feature checks
• 0.1.7 April 2022: Perf improvement for Windows CoW link creation by reducing kernel round-trips
• 0.1.6 April 2022: Perf improvement for all Windows APIs
• 0.1.5 October 2021: Separate exception type for when link limit is exceeded. Mac and Linux throw NotSupportedException.
• 0.1.4 October 2021: Fix doc XML naming. Mac and Linux throw NotSupportedException.
• 0.1.3 October 2021: Bug fixes for Windows. Mac and Linux throw NotSupportedException.
• 0.1.2 October 2021: Performance fixes for Windows. Mac and Linux throw NotSupportedException.
• 0.1.1 October 2021: Bug fixes for Windows. Mac and Linux throw NotSupportedException.
• 0.1.0 July 2021: Windows ReFS support. Mac and Linux throw NotSupportedException.

Related Works

• MSBuild SDK plugin to replace Copy task with one that supports CoW: https://github.com/microsoft/MSBuildSdks/tree/main/src/CopyOnWrite
• CoW now available in the Microsoft.Build.Artifacts MSBuild SDK plugin to speed up file copies for artifact staging.
• Rust CoW: https://github.com/nicokoch/reflink

Contributing

This project welcomes contributions and suggestions. See CONTRIBUTING.md.

Running Unit Tests on Windows

If you have a local ReFS drive volume on which to run ReFS related tests, set the following user or system level environment variable:

CoW_Test_ReFS_Drive=D:\

(You may need to exit and restart VS, VSCode, or consoles after setting this.) When this env var is not available, unit tests create and mount a local ReFS VHD for testing. You must run tests elevated (as admin), e.g. by opening Visual Studio as an admin before opening the solution.

Performance Comparisons

Windows

The following tests on various versions of Windows compare System.IO.File.Copy() with CloneFile(), 50 copies/clones of a single source file per measurement, highest performance clone flags and settings. Defender real-time scanning was disabled in the test directory. See CoWComparisons.cs. Machine was an 8/16-core with NVMe.

Windows 11 Prerelease 2H23 with Dev Drive

Dev Drive is a new evolution of the ReFS filesystem starting in the Windows 11 23H2 refresh. It was announced at Microsoft Build 2023, and features significantly faster execution vs. 22H2 ReFS or NTFS along with CoW support and a performance mode for Defender antivirus. More details can be found here.

CoW links on Dev Drive take approximately constant time except at large file sizes. The savings is proportional to the file size, with 16MB files at about 31X performance, 1MB at 5.9X, and small sizes at about 2X. Note that all performance numbers are significantly better than the no-VHD 22H2 measurements at the bottom of this page, reflecting the Windows Filesystem team's work to reduce overhead for Dev Drive.

The Windows Insider build used for testing was from early May, 2023.

Windows 11 release 2H22

Detailed numbers for a VHD formatted empty with ReFS for each iteration. 16MB files are about 35X performance, 1MB at 3.2X, and small sizes at about 1.3X.

Same benchmark performed on a ReFS partition (no VHD) on the NVMe disk: