On Mon, Aug 30, 2021 at 08:09:38PM +0100, Matthew Wilcox wrote: > On Mon, Aug 30, 2021 at 07:59:17PM +0200, Jean-Pierre André wrote: > > The NTFS-3G project globally aims at providing a stable NTFS driver. The > > project's advanced branch has specifically aimed at developing, maturing, > > and releasing features for user feedback prior to feature integration into > > the project's main branch. > > So do I understand correctly ... > > - We have an NTFS filesystem from Anton Altaparmakov in fs/ntfs which was > merged in 1997 and is read only. > - We have Paragon's NTFS3 in the process of being merged > - We have Tuxera's NTFS-3G hosted externally on Github that uses FUSE > > Any other implementations of NTFS for Linux that we should know about? > Is there any chance that the various developers involved can agree to > cooperate on a single implementation? I would also like to here about this from ntfs-3g guys. What do you even think about this whole ntfs3 kernel driver? My own opionion is that kernel really needs ntfs driver at it's own because it will greatly benefit growing iot device market and also maybe it will be in Android in same day. Also great performance boost with ntfs3 compared to ntfs-3g. It will be strange situation that we continue development from both sides. ntfs-3g guys have only open source NTFSPROGS tools what is available. I like to note, that Paragon has sayd that they will open source their mkfs and fschk, but I will not count on that. That means that then there will be two tool set also. This is not good for users. After ntfs3 is merged to mainline we are three driver situation. Hopefully kernel ntfs driver can be dropper in year or two. One thing what we should at least share is testing. There is work that has been done for xfstests that ntfs3 and ntfs-3g will be supported: lore.kernel.org/fstests/YQoVXWRFGeY19onQ@xxxxxxx/ Xfstests will support also other fuse base drivers. lore.kernel.org/fstests/20210812045950.3190-1-bhumit.attarde01@xxxxxxxxx/ There is already support for ntfs3 and ntfs-3g for kvm-xfstests. This was done so that we know how these compare to each other. And can help decissions that is ntfs3 ready for mainline. github.com/tytso/xfstests-bld/commit/fa6410d922d38735a5f69345221f8eacb3ae1af I do think that if ntfs3 will be solid and some remaining bugs will be solved it would make no sense to use ntfs-3g. So what do you think about all of this? Best regards Kari Argillander
