Package Details: ntfs3-dkms 1:5.17-1

Git Clone URL: https://aur.archlinux.org/ntfs3-dkms.git (read-only, click to copy)
Package Base: ntfs3-dkms
Description: NTFS3 is fully functional NTFS Read-Write driver. The driver works with NTFS versions up to 3.1.
Upstream URL: https://www.kernel.org/doc/html/latest/filesystems/ntfs3.html
Licenses: GPL2
Conflicts: ntfs3
Provides: ntfs3, NTFS3-MODULE
Submitter: rdnvndr
Maintainer: rdnvndr
Last Packager: Hanabishi
Votes: 37
Popularity: 1.26
First Submitted: 2020-08-16 11:43 (UTC)
Last Updated: 2022-03-29 14:57 (UTC)

Pinned Comments

Hanabishi commented on 2021-06-28 13:33 (UTC) (edited on 2022-06-28 11:38 (UTC) by Hanabishi)

Note: the driver was merged to the upstream kernel in 5.15. So this package is useless for Arch official kernels.
If you want bleeding edge updates, use ntfs3-dkms-git.

Readme
More info and tips
How to use DKMS modules
Paragon NTFS3 FAQ

doug commented on 2020-09-09 07:24 (UTC) (edited on 2020-09-09 10:07 (UTC) by doug)

I made some test using bonnie and pts, this driver seems to be much faster than ntfs-3g

http://moodle.math.sk/~doug/bonnie_ntfs3_paragon.html

http://moodle.math.sk/~doug/bonnie_ntfs-3g.html

(disregard the read tests, since they were done from page cache)

edit: compilebench in pts, now includes native ext4, the paragon ntfs3 driver performance is comparable

https://openbenchmarking.org/result/2009092-NE-NTFSCOMPA56

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 16 Next › Last »

jpegxguy commented on 2021-04-28 13:30 (UTC)

Ah, so kernel_version_fix.patch was added because ntfs3 was normally based on 5.12 in the mailing list? Thanks for the quick answer

Hanabishi commented on 2021-04-28 13:28 (UTC) (edited on 2021-04-28 13:29 (UTC) by Hanabishi)

@jpegxguy, because it contains a patch for 5.11 or lower. Just wait when main linux package from core repo will be updated to 5.12, then I will update this package too.
Or if you want it right now, just remove

patch -p3 -N -i "$srcdir/kernel_version_fix.patch"

line form the PKGBUILD.

jpegxguy commented on 2021-04-28 13:23 (UTC)

5.12 build error (I'm using linux-ck but I don't it's related):

DKMS make.log for ntfs3-26.0.0 for kernel 5.12.0-1-ck-zen (x86_64)
Τετ 28 Απρ 2021 04:22:09 μμ EEST
make -C /lib/modules/5.12.0-1-ck-zen/build M=/var/lib/dkms/ntfs3/26.0.0/build modules
make[1]: Entering directory '/usr/lib/modules/5.12.0-1-ck-zen/build'
  CC [M]  /var/lib/dkms/ntfs3/26.0.0/build/attrib.o
  CC [M]  /var/lib/dkms/ntfs3/26.0.0/build/attrlist.o
  CC [M]  /var/lib/dkms/ntfs3/26.0.0/build/bitfunc.o
  CC [M]  /var/lib/dkms/ntfs3/26.0.0/build/bitmap.o
  CC [M]  /var/lib/dkms/ntfs3/26.0.0/build/dir.o
  CC [M]  /var/lib/dkms/ntfs3/26.0.0/build/fsntfs.o
/var/lib/dkms/ntfs3/26.0.0/build/fsntfs.c: In function ‘ntfs_bio_fill_1’:
/var/lib/dkms/ntfs3/26.0.0/build/fsntfs.c:1623:24: σφάλμα: ‘BIO_MAX_PAGES’ undeclared (first use in this function); did you mean ‘BIO_MAX_VECS’?
 1623 |   new = ntfs_alloc_bio(BIO_MAX_PAGES);
      |                        ^~~~~~~~~~~~~
      |                        BIO_MAX_VECS
/var/lib/dkms/ntfs3/26.0.0/build/fsntfs.c:1623:24: σημείωση: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [scripts/Makefile.build:271: /var/lib/dkms/ntfs3/26.0.0/build/fsntfs.o] Error 1
make[1]: *** [Makefile:1855: /var/lib/dkms/ntfs3/26.0.0/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.12.0-1-ck-zen/build'
make: *** [Makefile:40: all] Error 2

eNV25 commented on 2021-03-29 10:17 (UTC)

@Hanabishi Yea, I didn't notice.

Hanabishi commented on 2021-03-29 10:04 (UTC) (edited on 2021-03-29 10:05 (UTC) by Hanabishi)

@eNV25, sadly no. The patchwork is broken. Look closely, you will see that the message #4 was just lost there.
https://i.ibb.co/QDMGTpF/image.png

post-factum commented on 2021-03-27 22:40 (UTC)

Incremental diff between v24 and v25: https://gitlab.com/post-factum/pf-kernel/-/commit/53c3b8a7ea40260500d85e6e9816513e0d4a70ca

Let me know if I missed something. This is compile-tested only ATM.

Hanabishi commented on 2021-03-01 21:51 (UTC) (edited on 2021-03-01 21:51 (UTC) by Hanabishi)

@babam, our problem is fixed in v22, congrats!
@post-factum, I've made a new patch by my own taking yours as example, thanks again.

babam commented on 2021-02-13 20:30 (UTC)

Here is a file access problem on my system https://tinyimg.io/i/UdLDQkQ.png

Hanabishi commented on 2021-02-13 10:21 (UTC)

@ignapk, not a bug. NTFS itself supports any characters, such illegal characters is just Windows restriction. Also ntfs supports case-sensitive names (and Windows 10 supports it too since WSL was introduced).
Yes, for NTFS-3G there is optional flag windows_names. You can send a such feature request to the driver devs if you want.

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 16 Next › Last »