Linux kernel -stable discussions
 help / color / mirror / Atom feed
* [REGRESSION][NTFS] Linux 7.3.4 mounts 64K-cluster NTFS read-only after $MFTMirr record 24 mismatch
@ 2026-11-20 12:49 d3nchk
  2026-11-20 14:26 ` liubaolin
  2026-11-20 20:39 ` Sasha Levin
  0 siblings, 2 replies; 3+ messages in thread
From: d3nchk @ 2026-11-20 12:49 UTC (permalink / raw)
  To: ntfs@lists.linux.dev
  Cc: linkinjeon@kernel.org, hyc.lee@gmail.com, zenghongling@kylinos.cn,
	regressions@lists.linux.dev, stable@vger.kernel.org

Hello,

Resending in plain text because the previous HTML-formatted message was rejected by the regressions mailing list. Apologies if this creates duplicates for other recipients.

I am reporting a regression in the in-kernel fs/ntfs driver (NOT ntfs3).

Environment:
- Distribution: Debian 13, backports kernel
- Working kernel: 7.2.12
- Broken kernel: 7.3.4+deb13-amd64
- Device: /dev/nvme0n1p1
- Filesystem: NTFS 3.1
- Cluster size: 65536 bytes
- Mount options: defaults (including errors=continue)
- Driver: fs/ntfs/ntfs.ko.xz

Kernel log:

ntfs: (device nvme0n1p1): check_mft_mirror(): $MFT and $MFTMirr record 24 do not match. Run chkdsk.
ntfs: volume version 3.1, dev nvme0n1p1, cluster size 65536
ntfs: (device nvme0n1p1): load_system_files(): Errors were recorded during mount. Mounting read-only. Run chkdsk.

This volume worked read-write with kernel 7.2.12. After upgrading to 7.3.4, it is forcibly mounted read-only, making normal file operations impossible.

Windows chkdsk has been run repeatedly, both through the GUI and command line, including dismounted-volume checks. The issue persists after rebooting into Linux.

I suspect commit 749357bd48c16c4cdc09093450deca609492f012 introduced the new read-only behavior for this case.

There is also a potentially relevant NTFS compatibility issue: modern Windows may not keep all $MFTMirr records synchronized on volumes with large clusters. Here the mismatch is reported at record 24, beyond the first 16 records.

Please investigate:

1. Whether the comparison of MFT mirror record 24 is valid for modern Windows-created NTFS volumes with 64K clusters.
2. Whether this is a false-positive filesystem corruption report.
3. Whether errors=continue can be honored for noncritical MFT mirror mismatches, while retaining mandatory read-only protection for Windows hibernation and genuinely unsafe filesystem states.
4. Whether a fix can be backported to the Linux 7.3 stable series.

This regression prevents normal read-write access to this volume.

Thank you.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-11-20 20:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20 12:49 [REGRESSION][NTFS] Linux 7.3.4 mounts 64K-cluster NTFS read-only after $MFTMirr record 24 mismatch d3nchk
2026-11-20 14:26 ` liubaolin
2026-11-20 20:39 ` Sasha Levin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox