You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I have read on it, the major issue supporting NTFS has been the NTFS-3G FUSE driver. That said, at least in my tests, fstransform does work both ways (albeit I needed to manually specify source file system). Now that Ubuntu 22.04 will use kernel 5.15 (which has a new in-kernel driver NTFS3), I think its support will be super useful
The text was updated successfully, but these errors were encountered:
Very good :)
I was following the kernel mailing list [email protected], and after a lot of sustained traffic for NTFS3 technical discussion, last december it became very quiet - I take it means the integration is complete.
I am currently somewhat stuck on kernel 5.14 for technical reasons (due to work-from-home, I have a complex setup that is cumbersome to upgrade) but I'll try to switch to 5.15 or 5.16 and test the combination fstransform + NTFS3
I have upgraded my installation and tested conversion using the new NTFS3 driver.
It's very fast, but it seems sparse files are not supported (!)
Furthermore, the driver is already orphaned, as the author is no longer responding on linux-ntfs-dev mailing list or on other channels.
Both problems are unexpected and will significantly delay support for NTFS3 in fstransform - and likely for other applications too.
Lack of sparse file is really surprising. Pretty sure ntfs-3g fuse driver supported sparse files, though it is fuse. Also no communication puts a damper on the NTFS3 driver. This is really unfortunate as having a proper in-kernel driver for NTFS was actually good news.
From what I have read on it, the major issue supporting NTFS has been the NTFS-3G FUSE driver. That said, at least in my tests, fstransform does work both ways (albeit I needed to manually specify source file system). Now that Ubuntu 22.04 will use kernel 5.15 (which has a new in-kernel driver NTFS3), I think its support will be super useful
The text was updated successfully, but these errors were encountered: