Since I started using the NTFS3 kerneldriver almost a year ago (GPL-driver created by Paragon software) I sometimes end up with corrupted filesystems. This has happened several times since I started using it.
I know that several people seem to have issues with it:
see: Ntfs3 keeps corrupting my ntfs partitons - Support - Manjaro Linux Forum
and: Does the Linux NTFS3 Driver Corrupt Directories? - Heiko's Blog
But I tried to sit it out and see how things would develop. ... Until today!
This time it was a whole 2TB (external) disk filled for 75% with data that corrupted and this time also beyond normal recovery.
(To whom it may concern: Kernel 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux)
It wouldn't mount. It recognized the disk and partitiontable but that was all.
Tried it on a MS-windows OS and it timed out after minutes of trying.
MS-Windows couldn't even recognize the disk itself !
Testdisk would have been able to save a lot though...maybe even everything.
Since I have a duplicate backup I luckily didn't need to go that way. I can just
cp -a /media/xxx/source/. /media/xxx/target/
to a spare disk.
But this is the last time I endured the shenennigans of this driver.
This incident caused me to no longer trust this (now standard) Paragon NTFS3 kerneldriver. I revert back to the userspace fuseblk ntfs-3g driver which is, although slower, more reliable on my setup.
If you are curious into what I do to revert to ntfs-3g: I use just one command:
echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf
Goodby buggy kerneldriver.