My experience of using NTFS on Linux was downloading a torrent on a dual boot laptop and it shutting down due to overheating. This was more than a decade ago, so hopefully it’s a lot better by now.
Reading from NTFS is nearly flawless. Writing and actively using it is pretty bad occasionally though, to the point where steam doesn’t support it and recommends against it for game libraries on Linux.
That may be an old issue, but I just set up a couple of NTFS drive Steam libraries on Linux last week and it didn’t give me any errors or warnings about the drive format. But I did have big issues with the Flatpak edition of Steam - it couldn’t even write to a local second ext4 partition. Had to switch to .deb Steam install to fix all that
You might know this already, but some (all?) flatpaks are denied access to most drives in the system. I’ve used Flatseal to address that issue when it comes up, though there may be better ways.
Yes I did read up on that and tried using Flatseal for permissions granting, but it didn’t work so I didn’t troubleshoot it very far before doing to the .deb install
Nah, the same thing was fine under windows. The old linux ntfs driver was just horribly inefficient and 100%'ed the cpu for too long. The hardware worked as intended - it shut down to avoid thermal damage. Possibly there was some lower “speedstep” the OS could have told the CPU to use, but that didn’t seem to happen on this combination of OS and hardware.
Running at 100% CPU for any amount of time should be fully expected by the manufacturer and should ramp up fans and throttle the CPU if necessary. Those are hardware functions.
Just to add on to your comment: Hardware should not “shut down” due to software operations. Max fan speed and execution slow down, yes, but not a shut down, unless your computer has a function of shutting down when getting hot. Normal operation should just keep going.
Emergency thermal shut-off is a very common function in various pieces of computer hardware. And if throttling doesn’t help it should indeed shut down, rather than cause damage.
My experience of using NTFS on Linux was downloading a torrent on a dual boot laptop and it shutting down due to overheating. This was more than a decade ago, so hopefully it’s a lot better by now.
The heating feature is actually a critical part of my workflow.
I’ve been transferring files from old NTFS drives formatted for Windows on a Debian machine without issue.
Reading from NTFS is nearly flawless. Writing and actively using it is pretty bad occasionally though, to the point where steam doesn’t support it and recommends against it for game libraries on Linux.
My experience was miserable attempting to do so, to the point that it was better to just nuke everything across 4 drives and start over
That may be an old issue, but I just set up a couple of NTFS drive Steam libraries on Linux last week and it didn’t give me any errors or warnings about the drive format. But I did have big issues with the Flatpak edition of Steam - it couldn’t even write to a local second ext4 partition. Had to switch to .deb Steam install to fix all that
You might know this already, but some (all?) flatpaks are denied access to most drives in the system. I’ve used Flatseal to address that issue when it comes up, though there may be better ways.
Yes I did read up on that and tried using Flatseal for permissions granting, but it didn’t work so I didn’t troubleshoot it very far before doing to the .deb install
That sound more like a hardware issue, no?
Nah, the same thing was fine under windows. The old linux ntfs driver was just horribly inefficient and 100%'ed the cpu for too long. The hardware worked as intended - it shut down to avoid thermal damage. Possibly there was some lower “speedstep” the OS could have told the CPU to use, but that didn’t seem to happen on this combination of OS and hardware.
Running at 100% CPU for any amount of time should be fully expected by the manufacturer and should ramp up fans and throttle the CPU if necessary. Those are hardware functions.
Just to add on to your comment: Hardware should not “shut down” due to software operations. Max fan speed and execution slow down, yes, but not a shut down, unless your computer has a function of shutting down when getting hot. Normal operation should just keep going.
Emergency thermal shut-off is a very common function in various pieces of computer hardware. And if throttling doesn’t help it should indeed shut down, rather than cause damage.