You are not logged in.
Hello everyone! I had a little problem mounting an ntfs volume with the Paragon driver that is built into the Linux kernel. I'm using dual boot (Windows 11 and Arch LInux). Therefore, in order to have access to the disks, it is important for me to save ntfs. I used my user's uid and gid. The user owns all the files on the ntfs disk, but has the “View contents only” permission for the owner. And this prevents applications that use this disk from working properly. But the user can change the permissions, and hence I can get full access to the file by changing the permission. But when I boot into Windows and then back into Linux, all file permissions are reset and become "Content View Only" again. And again we have to change the permissions of the necessary files. Is it possible to somehow mount this ntfs partition so that initially the user has full access to the files, or simply disable the access rights system for the ntfs disk?
Here is my fstab:
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 / btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvolid=256,subvol=/@ 0 0
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 /home btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvol=/@home 0 0
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 /.snapshots btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvol=/@snapshots 0 0
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 /swap btrfs relatime,discard,autodefrag,compress=zstd:9,subvol=@swap 0 0
# swapfile
/swap/swapfile none swap sw
# /dev/nvme1n1p3
UUID=16D1-1B6C /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
/dev/mapper/bitlocker1 /media/mount/bitlocker1 ntfs3 uid=1000,gid=1000,dmask=027,fmask=137 0 0
/dev/mapper/bitlocker2 /media/mount/bitlocker2 ntfs3 uid=1000,gid=1000,dmask=027,fmask=137 0 0
Last edited by Afmer (2024-01-21 12:47:33)
Offline
Hi, perhaps you will have better luck with the ntfs-3g package?
I set up my ntfs disk as follows in fstab and have no problems with permissions or changes thereof:
UUID=3E918021379019D7 /run/media/user/WINDISK ntfs-3g defaults 0 0
Only one thing is certain: nothing is certain.
Offline
Use the
noacl
mounting option to make the driver ignore the permission logistics.
Offline
Hi, perhaps you will have better luck with the ntfs-3g package?
I set up my ntfs disk as follows in fstab and have no problems with permissions or changes thereof:
UUID=3E918021379019D7 /run/media/user/WINDISK ntfs-3g defaults 0 0
Unfortunately, performance on ntfs-3g is much lower than that of the paragon driver
Offline
Use the
noacl
mounting option to make the driver ignore the permission logistics.
I added noacl to fstab, but it didn't have any effect.
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 / btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvolid=256,subvol=/@ 0 0
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 /home btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvol=/@home 0 0
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 /.snapshots btrfs rw,noatime,compress=lzo,ssd,space_cache=v2,subvol=/@snapshots 0 0
# /dev/mapper/cryptroot LABEL=cryptroot
UUID=1eea2ab2-4a25-4133-8fae-9c733065fc86 /swap btrfs relatime,discard,autodefrag,compress=zstd:9,subvol=@swap 0 0
# swapfile
/swap/swapfile none swap sw
# /dev/nvme1n1p3
UUID=16D1-1B6C /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
/dev/mapper/bitlocker1 /media/mount/bitlocker1 ntfs3 uid=1000,gid=1000,dmask=027,fmask=137,noacl 0 0
/dev/mapper/bitlocker2 /media/mount/bitlocker2 ntfs3 uid=1000,gid=1000,dmask=027,fmask=137,noacl 0 0
Offline
1. You have to use windows inbetween, rebooting leaves the permissions intact?
2. Can you test a non-bitlocker partition?
3. What do the permissions on windows (after a direct reboot)?
4. 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
Offline
I understood what the problem was. It had to do with custom icons for folders in Windows. I noticed that not all directories had "Read-only" access. Only those directories with custom icons had read-only access. The issue arose with the Yandex Disk directory. Upon startup, Yandex Disk on Windows always sets its own icon for the folder. Therefore, after booting into Windows and switching back to Linux, the permissions were disrupted. Perhaps there is some other change in metadata that affects this, but in my case, it was the custom icons. After removing all custom icons and preventing Yandex Disk from launching at Windows startup, everything worked as it should.
Offline