I use a 500GB SSD for my Download folder and the disk is shared with a Windows system too. I never noticed any issue, I’m using NTFS3 since it is available, and use torrents a lot on it. I don’t use the same fstab options though.
ExFAT is universally supported. (Samsung is the main developer for exfatprogs, which is important for Android devices as well.) ExFAT is here to stay with universal compatibility across Linux, macOS, Windows, and mobile devices.
As in you’re installing applications to the partition? I’ll be honest, this is an odd “hybrid” setup you’ve got going.
Then out of curiosity, do you have preallocation enabled with qBittorrent?
Finally, to rule out a more serious underlying issue, I must second @maycne.sonahoz’s recommendation to check the SMART logs and even run a short (or preferably extended) SMART selftest.
To add to this, I’ve owned two WD Blue drives that both catastrophically failed within 30 days of purchase. Two different drives. Two different occasions. Both purchased brand new from Amazon (not from a third-party seller, but legit from Western Digital.)
the recommended mounting options for ntfs3 include both noatime,prealloc. this might specially apply for torrenting.
i had issues where qbitorrent quit on a ntfs3 mount when onetime i had a powerloss while torrenting. the NTFS partition was corrupted, and could only be fixed by chkdsk /f in windows. also if you are using ntfsfix always use the ‘-d’ flag, any check without the -d flag make the NTFS partition marked as being dirty, which could lead to the partition being at worse being unmountable or lead to other issues with ntfs3. ntfs-3g somehow seems to work nevertheless.
ntfs3 implementation is still rough on the edges, worse its not maintained for sometime now, so dont expect the current issues to go away soon.
like others have suggested exfat is recommended if you can switch.
I’m using the same config as @omano and included the prealloc option now, did a quick test and no issues so far, but it doesn’t always present itself immediately so I’ll keep reporting whatever happens in the next few weeks.
There is an open issue i just found, im dumb i was search qbittorrent issue tracker… so the devs are aware of this issue, but reading that thread you’ll see that ntfs-3g works, its ntfs3 that is presenting this issue, i’ve been using fuse on linux for years and never ever had this issue before.
fairly common setup, if you want to share a large partition and the same files between windows and linux the easiest way is to use NTFS, especially for gaming.
ive considered using exfat before, but data loss is a real concern for me.
For sharing and accessing files between Linux and Windows? Agreed. But what you’re describing is installing software and games to this partition. You’re not just sharing files (like images, videos, documents, etc.) The software installed by one system is useless to the other system.
For OS-interoperability, exFAT is safer (and less complex) than NTFS. (See @koshikas’s post above.)
Just make sure you remove exfat-utils and install exfatprogs (developed by Samsung).
Do you have preallocation enabled with qBittorrent?
That makes more sense, and you shouldn’t have (more) problems with Steam games stored on exFAT. Years ago Valve removed the pointless “small games only” limitation for exFAT filesystems, because they were treating FAT32 and exFAT the same.
So what are the odds? I now experienced twice a NTFS error that I had to boot to Windows to “checkdisk” and fix.
But I still am not sure this is related to qbitorrent. I know it was started (but not downloading) the first time I crashed, not sure about the second, but it crashed when I moved my computer case (image froze, sound continued playing for ten seconds, then total freeze no TTY nothing), and the only issue I find in journal is an Nvidia issue about the GPU (total journal flood of similar lines omano-nvme kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x0000000f. I think the NTFS issue was caused because both crashes I electrically reset the computer, didn’t REISUB or cleanly shutdown the computer. I think this is what caused the NTFS issue forbidding boot because of the fstab entry for this NTFS disk, the NTFS file system was harmed in some way when I crashed and unplugged the computer to restart.
I also repasted my video card last week so maybe my video crash issue are related (I will loosen up the screws I went full tight).