Repository navigation
ntfs2refs 0.0.1-alpha: Windows boot volume, NTFS to ReFS in place (lab-qualified)
Pre-releasentfs2refs 0.0.1-alpha
A private experimental pre-release. It is not a production release.
This build converts an installed Windows 11 system partition from NTFS to ReFS
in place, and the converted installation boots to the desktop. It is qualified
on one lab virtual machine only. Make an independent backup before using it.
Build
- Source commit
3aaaf11bb4e5a4891942feeabc974d4188916e98(branch
codex/boot-volume), Rust 1.98.1,x86_64-pc-windows-msvc, release profile. ntfs2refs.exereports version0.1.0. SHA-256
e057c9e69554977167f47665c2a56425d0b77ab6f3a317f9174ed348af214492.
It is the executable that ran qualification run full-16 below; the only
commit after its build changed project documentation.lab-volume-manifest.exe, the separate tool that lists a volume before and
after conversion and compares the two listings. SHA-256
61b509b7b71aa9fc9d99cb15464ac1a3c0ceef2af8e89992037b78562b3bce92.
What was verified
Lab machine: Hyper-V generation 2 VM, Secure Boot on, 8 virtual processors,
24 GB of memory. Source: Windows 11 build 26300 on disk 0 partition 3 (64 GiB
disk, 22.9 GB used, 143,580 objects, 112,609 8.3 short names).
Each full run starts from the NTFS baseline checkpoint, converts from a
separate control OS, compares complete before/after listings made by
lab-volume-manifest, then starts the VM with only disk 0 attached and signs
in at the console.
| Run | Build | Conversion | Listing | Boot |
|---|---|---|---|---|
| full-16 | this executable | 28.0 min | identical, 0 differences | desktop; ReFS 3.14, 4 KiB clusters; winload.efi and refs.sys signatures valid |
| full-12 | same source, earlier build | 27.7 min | identical | desktop |
The same source also passed the 1-in-40 fixture twice (identical listings) and
--recover of a run stopped after apply. cargo test --locked --workspace --all-targets at the release commit: 713 passed, 0 failed, 52 ignored.
Differences the listing comparison allows, with their counts on the lab
volume: 112,609 short names that became links; NTFS compression flag removed
(218 files); System Volume Information content (8); kernel cache attributes
dropped (17,140).
How it was run
From a separate Windows installation (the control OS), with the partition to
convert attached as a data volume and not in use. In the lab it runs as
SYSTEM:
ntfs2refs.exe --drive D --windows-boot-volume --scratch-directory S:\runs --target-format dev-drive
D: is the NTFS Windows partition to convert. S: is a separate volume for
working files; the full run used about 30 GB of it. The converter takes the
source offline and holds it read-only until it has prepared and checked
everything. Nothing is written to the source before that point; a run that
stops earlier leaves the source unchanged, and is started again.
Before its first write the converter prints a recovery command with a
checksum. Keep it. If the run stops after it has started writing, complete
the conversion with:
ntfs2refs.exe --recover <printed directory> --recovery-sha256 <printed checksum>
Known limits
- Qualified on one VM and one Windows build. Not qualified on physical
hardware, other Windows builds, BitLocker, other partition layouts or larger
volumes. - Each 8.3 short name becomes a relative symbolic link beside its long name.
These are visible in Explorer:PROGRA~1inC:\, aMICROS~1icon on the
desktop. - The NTFS compression flag is not carried over; the files are stored
uncompressed. - A power cut during preparation is not resumed: start again.
- A full conversion of the lab volume takes 28 to 30 minutes on the lab host.
Assets
ntfs2refs-0.0.1-alpha-windows-x64.zip:ntfs2refs.exe,lab-volume-manifest.exeand these notes. SHA-2564966456f4c0bac93095cd6112a0eb5f06262842b3965ae6c7e86845cf17d713e(also in the.sha256file).ntfs2refs-0.0.1-alpha-source.zip:git archiveof tag0.0.1-alpha. SHA-25625bca3be312f3235334c5803cc6453236cddaa31cc8f537f02b33112409d72ca.
Recovered qualification records
The original full-16 console output and workspace test log have been recovered
and preserved in ntfs2refs-0.0.1-alpha-qualification.zip (SHA-256
6d7819d61cb0bfaa5b0cffbc73c137d876f31cc83bde811c3bc0eca29b9ab720).
The bundle contains source-line provenance and a hash manifest. The original
source and binary release assets above remain unchanged.
The original complete before/after JSONL files, verdict.json, raw trust-patch
records and desktop screenshot were not recovered. The bundle preserves actual
original command output; it does not fabricate those missing files. The separate
rec-04 run completed post-apply recovery and mounted healthy ReFS, but had no
before-listing and reported converted-not-compared. That result does not
establish full-content recovery, arbitrary interrupted writes or a Windows
boot-volume rollback matrix.
Integration closeout
The converter and corrected operating documentation were merged into main in
PR #27, commit
ab015130a04438a45df59b7601fbe0163dd84fb7.
Windows CI passed
formatting, Clippy, all workspace tests (713 passed, 52 ignored), and the complete
release build. The merged files exactly match the CI-tested merge tree.
Use the current operating guide
and qualification details.
The original release binaries, source archive and tag remain unchanged.
Additional evidence assets:
ntfs2refs-0.0.1-alpha-closeout-validation.zip: local checks and the independent
1-in-10 fixture listings and comparison, with zero unexpected differences.
SHA-2566c5f41619236d4759b1b7cd99d1ea54ba49787ca9caad37e6db12cf067fdbf27.ntfs2refs-0.0.1-alpha-ci-closeout.zip: complete hosted CI log, local test logs,
the test-only profiler synchronization fix and merge-tree verification.
SHA-256c2590b486e04ef7d8fc4e970304d1fa1251d69d67e7cc26f356c4a9ac942448d.
These checks do not expand the native hardware or recovery qualification scope
of the frozen alpha.