rmnscnce / ntfs3 Goto Github PK

ntfs3 Linux kernel module by Paragon Software

License: GNU General Public License v2.0

Makefile 0.20% C 99.80%

ntfs ntfs-driver linux dkms kernel-module module

ntfs3's Introduction

ntfs3

ntfs3 is a free (as in free beer and free speech) filesystem kernel module for Linux kernel that is developed by Paragon Software.

This unofficial out-of-tree module is tested to be compatible with Linux kernel 5.14 and later

Disclaimers

Authorship and copyright are held by Paragon Software GmbH, while rmnscnce is the maintainer of this "port", along with other contributors

Installation

Standard

make -j$(cat nproc) KVER=<your.kernel.version> # if left blank, it will build for the current running kernel
sudo make install

# To uninstall:
sudo make uninstall

DKMS (recommended)

Dependency: `dkms`

sudo make dkms # it will register the DKMS module and install for the current running kernel

# To uninstall:
sudo make dkms-uninstall

Bugs

※ Refer to MAINTAINERS for patch submission, bug fixes, etc.

Cannot mount the filesystem using the acl option (POSIX ACLs basically not working)

Documentation

(docs/ntfs3.rst)[docs/ntfs3.rst]:

=====
NTFS3
=====


Summary and Features
====================

NTFS3 is fully functional NTFS Read-Write driver. The driver works with
NTFS versions up to 3.1, normal/compressed/sparse files
and journal replaying. File system type to use on mount is 'ntfs3'.

- This driver implements NTFS read/write support for normal, sparse and
  compressed files.
- Supports native journal replaying;
- Supports extended attributes
	Predefined extended attributes:
	- 'system.ntfs_security' gets/sets security
			descriptor (SECURITY_DESCRIPTOR_RELATIVE)
	- 'system.ntfs_attrib' gets/sets ntfs file/dir attributes.
		Note: applied to empty files, this allows to switch type between
		sparse(0x200), compressed(0x800) and normal;
- Supports NFS export of mounted NTFS volumes.

Mount Options
=============

The list below describes mount options supported by NTFS3 driver in addition to
generic ones.

===============================================================================

nls=name		This option informs the driver how to interpret path
			strings and translate them to Unicode and back. If
			this option is not set, the default codepage will be
			used (CONFIG_NLS_DEFAULT).
			Examples:
				'nls=utf8'

uid=
gid=
umask=			Controls the default permissions for files/directories created
			after the NTFS volume is mounted.

fmask=
dmask=			Instead of specifying umask which applies both to
			files and directories, fmask applies only to files and
			dmask only to directories.

nohidden		Files with the Windows-specific HIDDEN (FILE_ATTRIBUTE_HIDDEN)
			attribute will not be shown under Linux.

sys_immutable		Files with the Windows-specific SYSTEM
			(FILE_ATTRIBUTE_SYSTEM) attribute will be marked as system
			immutable files.

discard			Enable support of the TRIM command for improved performance
			on delete operations, which is recommended for use with the
			solid-state drives (SSD).

force			Forces the driver to mount partitions even if 'dirty' flag
			(volume dirty) is set. Not recommended for use.

sparse			Create new files as "sparse".

showmeta		Use this parameter to show all meta-files (System Files) on
			a mounted NTFS partition.
			By default, all meta-files are hidden.

prealloc		Preallocate space for files excessively when file size is
			increasing on writes. Decreases fragmentation in case of
			parallel write operations to different files.

no_acs_rules		"No access rules" mount option sets access rights for
			files/folders to 777 and owner/group to root. This mount
			option absorbs all other permissions:
			- permissions change for files/folders will be reported
				as successful, but they will remain 777;
			- owner/group change will be reported as successful, but
				they will stay as root

acl			Support POSIX ACLs (Access Control Lists). Effective if
			supported by Kernel. Not to be confused with NTFS ACLs.
			The option specified as acl enables support for POSIX ACLs.

noatime			All files and directories will not update their last access
			time attribute if a partition is mounted with this parameter.
			This option can speed up file system operation.

===============================================================================

ToDo list
=========

- Full journaling support (currently journal replaying is supported) over JBD.


References
==========
https://www.paragon-software.com/home/ntfs-linux-professional/
	- Commercial version of the NTFS driver for Linux.

[email protected]
	- Direct e-mail address for feedback and requests on the NTFS3 implementation.

ntfs3's People

Contributors

Stargazers

Watchers

Forkers

cnguoyj manchangdangxiazh surfndez tmm1 antonio-petricca castiellian khalil-sleimi alexxxisanchezz cielavenir donmor liyafe1997 showgp

ntfs3's Issues

Silent corruption of filesystem

So i had a corrupted directory on my ntfs hdd, that is not a ntfs3 problem.

Here's the story.
I wanted to continue watching some videos on my ntfs hardrive in vlc. Played the most recent file. But then i looked in the directory with nemo(cinnamon file manager) and the files that i wanted to play next were not displayed. Funny thing was that the file that was currently playing in vlc was also missing in the directory.
Tried ls -la, find, su to root etc.. but it was'nt a hidden file/rights issue. Also with cp i could copy the file just fine using the absolute path.

Ran smartctl, fsck, badblocks even rkhunter and clamav.
But no problems.
Installed ntfs-3g ran ntfsfix but no issues there.
Then i mounted the drive with -t ntfs-3g and it came with my first error message (thought i saved it but can't find it anymore, sorry).

But here is a error message i did save:
$ ls /media/d_big/download-unsorted
ls: reading directory '/the/path': Input/output error

I had to chkdsk on grrr windows to fix this.
I hope you agree that the handling of the corrupted files in ntfs3 was an issue here.

edit:
Arch Linux kernel 6.0.2-arch1-1
Cinnamon 5.4.12

Windows symlinks not changing to the mounted place

Sorry if this is a noob question. I found that when using ntfs3 to mount a NTFS file system, all the symlinks created under Windows remain unchanged (i.e. still pointing to C:\path\to\file). However ntfs-3g would change the target paths to the mounted place like /mnt/WindowsDrive/path/to/file. And I wonder the reason of that.

My kernel is 5.16.3-zen1-1-zen.

Can't recover from halt

I installed ntfs3-dkms on manjaro and set it for my /home partition

# /etc/fstab
UUID=58C8-619C					/boot/efi	vfat    umask=0077 0 2
UUID=60f225a5-d96a-43db-a35d-49c6efad88f3	/		ext4    defaults,noatime 0 1
UUID=542F116A4C0961EB				/home		ntfs3	acl,discard,noatime 0 2
tmpfs						/tmp		tmpfs   defaults,noatime,mode=1777 0 0
/swapfile					none		swap    defaults 0 0

I have ssd. But if I halt my PC and then power-on, initramfs mounts all the partitions accept /home. Maybe this is not a bug but a config issue on my side. And don't worry I intentionally halted my test PC. No worries of loosing data here.

Directory Windows/System32/Config/ not visible at Win10H2

This seems to be a problem with characters of the ownership names, see below!

Mounting a (generated from german/deutsch ISO) Win10 Partition with mount -t ntfs3 .. results in a nonexistent Config-directory in Windows-dir. The System was built in a qemu environment, 64bit.
The system was modified with
powercfg /H off

before shutting down. The mount command was
mount -t ntfs3 -o offset=$[512*104448],showmeta,no_acs_rules,nls=utf8 /dev/gu/win10unattend /mnt

Mounting with -o ntfs-3g results in an existing Config/ Dir.
Furthermore, looking at the dir wir "ls", the config-dir ist visible, but not accessible:

root@p51:/mnt/Windows/System32# ls -lh | grep -i config
ls: Zugriff auf 'de' nicht möglich: Datei oder Verzeichnis nicht gefunden
ls: Zugriff auf 'config' nicht möglich: Datei oder Verzeichnis nicht gefunden
...
-rwxr-xr-x 2 root root 146K Dez 7 2019 AppManagementConfiguration.dll
d????????? ? ? ? ? ? config
-rwxr-xr-x 2 root root 686K Nov 19 03:49 configmanager2.dll
..

Trying the same with the englisch-international version of win10 seems running fine! The difference is imho the names of the ownership, i.e. the owner of ther config/ dir is "AUTORITÄT/SYSTEM" (with the special character "Ä"), in english the same file has the ownership "AUTHORITY/SYSTEM" (with no special character).
Imho this is a hot candidate for the problem.

linux links in root or folder not usable

I have some ntfs partition. inside it i have linux links. but with ntfs3 instead fuse ntfs links to folders and files are not available.
must i do a screen?

/build...(bad exit status: 2); ERROR (dkms apport): binary package for ntfs3: v27_20210901.lore not found

Hey!
Trying to make dkms, but got error.

512yb@laptop:~$ make dkms -k 5.4.0-88-generic
mkdir -p /usr/src/ntfs3-v27_20210901.lore/
cp -R . /usr/src/ntfs3-v27_20210901.lore/
dkms add -m ntfs3 -v v27_20210901.lore

Creating symlink /var/lib/dkms/ntfs3/v27_20210901.lore/source ->
                 /usr/src/ntfs3-v27_20210901.lore

DKMS: add completed.
dkms build -m ntfs3 -v v27_20210901.lore

Kernel preparation unnecessary for this kernel.  Skipping...

Building module:
cleaning build area...
make -j16 KERNELRELEASE=5.8.0-55-generic -C /lib/modules/5.8.0-55-generic/build M=/var/lib/dkms/ntfs3/v27_20210901.lore/build...(bad exit status: 2)
ERROR (dkms apport): binary package for ntfs3: v27_20210901.lore not found
Error! Bad return status for module build on kernel: 5.8.0-55-generic (x86_64)
Consult /var/lib/dkms/ntfs3/v27_20210901.lore/build/make.log for more information.
make: *** [Makefile:58: dkms] Error 10
make: *** No rule to make target '5.4.0-88-generic'

How to solve this?

segmentation fault when trying to install Miniconda3

I have no idea why this is happening, but when trying to install Miniconda3 on my NTFS /home partition using their installer https://docs.conda.io/en/latest/miniconda.html#linux-installers, I get segmentation fault like so:

$ sh ./Miniconda3-py39_4.11.0-Linux-x86_64.sh
Welcome to Miniconda3 py39_4.11.0

In order to continue the installation process, please review the license
agreement.
Please, press ENTER to continue
>>>

...

Do you accept the license terms? [yes|no]
[no] >>> yes

Miniconda3 will now be installed into this location:
/home/jh2xl/miniconda3

- Press ENTER to confirm the location
- Press CTRL-C to abort the installation
- Or specify a different location below

[/home/jh2xl/miniconda3] >>> 
PREFIX=/home/jh2xl/miniconda3
Unpacking payload ...
Segmentation fault
Segmentation fault

I have verified that this is not an issue with my local environment by successfully installing Miniconda to my BTRFS root partition.

While unrelated, I am also unable to use https://github.com/abraunegg/onedrive on the NTFS partition, with it having Disk I/O error.

build failed on linux-5.12.11

Hi there! Great project. Is there are any plans to support 5.12? ntfs-3g is so slooooow.

[root@ivagulin-pc ntfs3]# make
make -C /lib/modules/5.12.11-300.fc34.x86_64/build M=/root/ntfs3 modules
make[1]: Entering directory '/usr/src/kernels/5.12.11-300.fc34.x86_64'
CC [M] /root/ntfs3/fsntfs.o
/root/ntfs3/fsntfs.c: In function ‘ntfs_bio_fill_1’:
/root/ntfs3/fsntfs.c:1620:38: error: ‘BIO_MAX_PAGES’ undeclared (first use in this function); did you mean ‘BIO_MAX_VECS’?
1620 | new = ntfs_alloc_bio(BIO_MAX_PAGES);
| ^~~~~~~~~~~~~
| BIO_MAX_VECS
/root/ntfs3/fsntfs.c:1620:38: note: each undeclared identifier is reported only once for each function it appears in
make[2]: *** [scripts/Makefile.build:271: /root/ntfs3/fsntfs.o] Error 1
make[1]: *** [Makefile:1857: /root/ntfs3] Error 2
make[1]: Leaving directory '/usr/src/kernels/5.12.11-300.fc34.x86_64'
make: *** [Makefile:46: all] Error 2

Access rights to files/folders (randomly?) return incorrect value, no matter if "no_acs_rules", usmask, fmask/dmask is set

When specifically mounting an NTFS drive with noacsrules, one can indeed write to files and folders, no matter what their respective NTFS permissions are.
However, when doing an ls, some folders and files return incorrect permissions from time to time like r-xr-xr-x.
This becomes problematic, whenever a program stat that directory/file and sees, that there is no w flag so it denies write access to it (even though it could according to noacsrules). Take e.g. a file manager like Dolphin: "right click/Create" is grayed out.

I expected permission masks to be the problem, but settings umask=0000 (same for f/dmask) do not fix the problem.

As a comparison between ntfs3 and ntfs-3g:

When mounting via ntfs-3g with the options rw,user,exec,uid=1000,gid=1000,umask=0000,fmask=0000,dmask=0000, all files and folders are set correctly to rwxrwxrwx.

drwxrwxrwx 1 klaus klaus        4096  9. Mai 21:53  Server
drwxrwxrwx 1 klaus klaus           0  4. Apr 07:03  SpeechRecognition
drwxrwxrwx 1 klaus klaus        4096 27. Mai 23:52  Spiele

When mounting via ntfs3 with the options rw,user,exec,uid=1000,gid=1000,noacsrules,umask=0000,fmask=0000,dmask=0000, I see this:

dr-xr-xr-x 1 klaus klaus        4096  9. Mai 21:53  Server
drwxrwxrwx 1 klaus klaus           0  4. Apr 07:03  SpeechRecognition
dr-xr-xr-x 1 klaus klaus        4096 27. Mai 23:52  Spiele

Note, that not all folders are missing the write-flag.
Also note, that ntfs-3g with no mount options set at all still shows these folders to be accessible as rwxrwxrwx

System Information
OS: Manjaro
Kernel: 5.10.59-1-MANJARO (LTS)
ntfs3 driver: https://aur.archlinux.org/packages/ntfs3-dkms-git/

ntfs3: sdc1: MFT: r=d77a4, expect seq=c146 instead of c134!

it show msg like this on my machine
related files can't not be accessed, move, or delete
ntfsfix -b -d /dev/sdc1 show success msg, but doesn't help