2 ms·
The FUSE one (ntfs-3g) is fine - we use it for bulk editing Windows VMs when transferring them from VMware to KVM[1]. Unfortunately development has slowed to a
by rwmj 5y ago
The FUSE one (ntfs-3g) is fine - we use it for bulk editing Windows VMs when transferring them from VMware to KVM[1]. Unfortunately development has slowed to a standstill in the last few years. Which is a problem. At the moment it supports current Windows guests including relatively recent features like file compression, but we're only a MSFT new feature away from having to take over upstream development or look for an alternative. I doubt that an in-kernel driver will be noticably faster, but there's hope it might be more widely used and so better maintained.
[1] https://libguestfs.org/virt-v2v.1.html https://libguestfs.org/virt-v2v.1.html
- rincebrain 5y agoSure, I didn't mean to suggest there was anything fundamentally flawed about ntfs-3g, I've used it to basically universal success after the first year or two after it was released, just that it is FUSE, which means there's always going to be some overhead involved that wouldn't be present in an in-kernel driver (though they keep trimming away at how much that has to be). https://jp-andre.pagesperso-orange.fr/changelog.html https://jp-andre.pagesperso-orange.fr/changelog.html doesn't seem totally dead, though the github repo hasn't seen much since March (but I don't think "since March" is what you meant by "last few years").