I’m running EndeavourOS and Windows 11. Each OS is on a separate disk, but I have a data disk that is currently NTFS that mount in both OSes. NTFS causes problems for some things in Linux, and I’m worried it’ll bork the drive for windows eventually, so I’m keen to find an alternative. I’ve read about the WinBTRFS driver so wondering if that is a better way to go?

I don’t want to run a server with a share to access this data because it is way to slow for my needs.

32 points

NTFS is considered pretty stable on Linux now. It should be safe to use indefinitely.

If you’re worried about the lack of Unix-style permissions and attributes in NTFS, then getting BTRFS or ext4 on Windows may be a good choice. Note that BTRFS is much more complicated than ext4, so ext4 may have better compatibility and lower risk of corruption. I used ext3 on Windows in 2007 and it was very reliable; ext4 today is very similar to ext3 from those days.

The absolute best compatibility would come from using a filesystem natively supported by both operating systems, developed without reverse engineering. That leaves only vfat (aka FAT32) and exfat. Both lack Unix-style permissions and attributes.

permalink
report
reply
6 points

sounds like my worries about NTFS reliability in Linux are more about historic reputation so I can probably relax on that front. The other issue with NTFS is performance in Linux is not great. FAT32 and exFat don’t like some filename characters from linux from what I read.

WinBTRFS is tempting. I have frequent backups so I might just give it a try and see what happens.

permalink
report
parent
reply
6 points

The NTFS3 driver in the kernel is about as fast as Ext4 ( and faster than Btrfs ).

permalink
report
parent
reply
2 points

Fuse driver of ntfs-3g yes it’s slow but if configurate to use ntfs3 it’s same fast as in windows

permalink
report
parent
reply
3 points
*

Didn’t know about ntfs3 so did some reading about it. There are some reports of corruptions, they were all fixed by letting windows do a chkdsk, and making sure the windows_names parameter when mounting the disk helped prevent problems.

I’m going to live with ntfs3 for a while as see what happens.

permalink
report
parent
reply
1 point

I use NTFS with Linux a lot, and have for years. The only issue I’ve ever had was Linux not being able to recover it properly after unsafely disconnecting it, but Windows fixed it just fine

permalink
report
parent
reply
4 points

If you’re worried about the lack of Unix-style permissions and attributes in NTFS

I’m pretty sure Linux still uses Unix-style permissions in NTFS, which causes issues when Windows tries to use its own permission system on the same partition.

permalink
report
parent
reply
1 point

Hi @Limonene@lemmy.world! It’s so hard to grasp as a casual user the actual benefits from file systems. I use ext4 on all my devices.

Could you point me to the required feature a file system needs to have in order to recover files after removing it with rm -rf?

I heard there are tools for my current file system which could help me out; But is there some file system with a rm-cache (until the disk is powered off or the cache is full).

Unix Permission is a must.

Would appreciate some general hints (I do replicate my personal important files).

permalink
report
parent
reply
14 points

DO NOT use WinBTRFS. It caused me some cryptic filesystem errors that I never found a real solution to. NTFS is the better option if you must have a shared disk, but I really suggest different partitions for each OS.

permalink
report
reply
5 points

They’re definitely not suggesting having both OSes in the same partition (even though that is technically possible using winbtrfs, it is objectively an insane thing to do).

permalink
report
parent
reply
1 point

I understood that just fine

permalink
report
parent
reply
2 points
*

Lol ok, then I guess I didn’t understand what the alternative would be when you suggested putting the OSes on different partitions.

permalink
report
parent
reply
11 points

I would use exFAT for a shared data drive. Just don’t use it for programs since it lacks unix file permission support.

permalink
report
reply
10 points

Please use different disks for each OS, you’ll save a lot of time and trouble later. It can be done, sure, but you’re setting yourself for a world of trouble in the future.

Just a recent issue

https://www.guru3d.com/story/dualboot-linux-systems-affected-by-grub-sbat-policy-changes-due-to-windows-update/

permalink
report
reply
4 points

OP is installing the OSes on separate disks. The common disk is for user data, not for the OS.

permalink
report
parent
reply
7 points
*

Most compatible is FAT32 which is also the most limited.

I am not sure I would trust the WinBtrfs driver with anything important. What problems are you having with NTFS?

Linux has two NTFS stacks: NTFS-3G and NTFS3 ( in the Linux kernel since 5.15 ). NTFS3 is faster and more feature rich I think but that said it also lacks a few things. NTFS-3G is more mature and some people still report it to be more stable.

permalink
report
reply

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

Community stats

  • 8.3K

    Monthly active users

  • 6.3K

    Posts

  • 173K

    Comments