| 28 Sep 2022 |
 Orange Bomb | I tried using NTFS3 instead of ntfs-3g to mount my Windows disk. It had strange results. | 04:32:00 |
| Orange Bomb | The "root" of the disk was fine, but I had no write permissions in any directories. | 04:32:29 |
 drgibbon | Oh yeah? I used it once, was smooth sailing from memory. | 04:33:19 |
| drgibbon | Mounted with the correct options yeah? You have to specify it somehow, I can't remember exactly. | 04:34:22 |
| Orange Bomb | -t ntfs3, right? | 04:34:37 |
| drgibbon | In reply to @drgibbon:matrix.org
Seems to run quite well, I was using ntfs3 in /etc/fstab which forces it, also mount -t ntfs3 makes it use the new driver instead of the fuse one. Turns out in the end I don't need it (I'm glad not to have to deal with NTFS), but cool to know that it's there. OK, good search on Matrix :) mount -t ntfs3 | 04:35:16 |
| Orange Bomb | I had it written as /dev/sda1 /ntfs ntfs3 fmask=111,dmask=000 1 0 in my fstab file. | 04:35:31 |
| drgibbon | any luck with commenting it out of fstab and just trying different mount options? | 04:36:05 |
| Orange Bomb | Which, aside from a 3, is identical to how I used the FUSE driver, and I'm pretty sure how Slackware auto-configured it last year. | 04:36:08 |
| Orange Bomb | My only guess is that the new driver is doing a better job at following NTFS permissions, and thus is locking me out of "my" files. | 04:36:54 |
| Orange Bomb | Trying to search for details about this have proven difficult, because it's picking up keywords from unrelated issues. | 04:38:14 |
| Orange Bomb | Stupid search engines. | 04:38:18 |
| Orange Bomb | This partition already has problems with the "dirty bit" and isn't permanently clearing it. | 04:39:02 |
| Orange Bomb | This was a non-issue until involving Steam, wherein it's the source of all kinds of silent failures. | 04:42:54 |
| drgibbon | Does using noacsrules work? https://docs.kernel.org/filesystems/ntfs3.html | 04:44:00 |
| drgibbon | Also something here, not much though https://unix.stackexchange.com/questions/678880/how-can-i-mass-set-the-permissions-of-existing-files-in-the-new-ntfs3-driver | 04:45:35 |
| Orange Bomb | I think it's got to do with the umasks being set. | 04:51:43 |
| Orange Bomb | It looks like noacsrules works. | 04:56:20 |
| Orange Bomb | No clue if it's going to gore the permissions as time goes on, but I'm pretty sure I'm not returning to Windows. | 04:56:40 |
| Orange Bomb | I could maybe also assign the disk to my user instead of root. | 04:57:58 |
| Orange Bomb | Does fsck work on NTFS volumes? | 05:01:23 |
| Orange Bomb | I haven't given this partition a proper look-over for over a year. | 05:01:45 |
| Orange Bomb | I look forward to the day that I blast this fucker out and write in Btrfs or something in its place. | 05:03:50 |
| drgibbon | Sorry, no idea about using NTFS on Linux, I tried it for a little bit when I was working to get a USB drive mounted on a router, but the router turned out to be so flaky that I gave up and just used a RPi instead. | 05:30:16 |
| Orange Bomb | I got more problems in Steam with writing permissions, so I gave up and reverted back to ntfs-3g. | 05:53:20 |
| Orange Bomb | I think I've spotted filesystem damage. | 08:06:35 |
 rbn | :< | 08:12:50 |
| Orange Bomb | The damage can only be repaired by Windows. | 08:26:50 |
|  @_bifrost_bub=40404.city:aria-net.org left the room. | 14:09:15 |
 marav | Element-desktop updated to 1.11.8
Noteworthy Feature
Bugfix
- Bump IDB crypto store version
Security fixes
- Fix for CVE-2022-39249
- Fix for CVE-2022-39250
- Fix for CVE-2022-39251
- Fix for CVE-2022-39236
| 16:32:04 |
