Fyi, it's somewhat common knowledge in tech circles that exFAT is an unreliable way of permanently sharing data between different operating systems: https://www.google.com/search?q=exfat+corruption+macos+windo...
exFAT is ok to use as a secondary file system for transferring/copying data between systems (aka "sneakernet") but not as a critical primary disk drive.
EDIT reply to : >the more reliable file system to use if different operating systems need to use it is UDF
UDF like exFAT does not have journaling feature in HFS+ and NTFS. Without journaling as a self-check feature, it makes the filesystem very fragile and prone to corruption. Similar to this explanation:
https://apple.stackexchange.com/questions/7609/what-are-the-...
For permanent data sharing between macOS/Windows/Linux, the more reliable setup than exFAT is network shares such as SMB/NFS mounts on a NAS with ZFS/btrfs filesystems. Unfortunately, that costs more money because of the extra hardware.
EDIT reply to: >If you just want to share files between 2-3 computers, by far the fastest and cheapest will be to wire the computers together over Thunderbolt.
When I researched the idea of daisy-chaining Thunderbolt with mac + Linux + Windows, I ran into stories saying it was not reliable. Example:
https://macperformanceguide.com/blog/2023/20230213_1022-Thun...
I could see where Thunderbolt daisy-chaining macos+Windows might work 100% perfectly for some but others have flaky issues because of various interactions of Thunderbolt chipsets, TB dock/hub quality, drivers, etc.
From what I understand, many eHDDs don't actually do this, instead reading the contents of the drive and exposing them to the computer by essentially emulating a USB flash drive. I would have to sniff the packets to be sure, but this is what I suspect my eHDD caddy is doing.
My main reason for wanting this is that, in some cases, it would make reading random drives substantially easier -- I have amassed a collection of HDDs that all have different partition schemes, filesystems, etc., and a fair number of those are unable to be processed by my caddy. This is a very frustrating experience, as a Linux device has some of the best filesystem / partitioning support in the world (and a random £15 caddy is obviously not going to provide very good competition.)
On the contrary, having the kernel process the HDD as a block device would most likely place it under marginally more computational stress (as opposed to the drive reading partition tables and filesystems itself), but I believe that's been fairly well-optimized by now.
On a positive note, I very much suspect the USB-C connector of being miles better than the Micro USB 3.0 interface my current caddy uses. In my experience, a bit of external force can easily encourage the connector out of the port.
> (and a random £15 caddy is obviously not going to provide very good competition.)
P.S. re this, I can sort of understand it, as the caddy came with a drive -- they clearly had the opportunity to optimize away support for filesystems that they weren't pairing the caddy with.
[0]: https://www.amazon.co.uk/SABRENT-enclosure-indicator-tool-fr...
https://www.amazon.co.uk/SABRENT-enclosure-indicator-tool-fr...
I'm a bit confused, but isn't eSATA exactly what you are looking for?
※ Listed on Amazon as "SABRENT 2.5-Inch SATA to USB 3.0 Tool-Free Clear External Hard Drive Enclosure [Optimized for SSD, Support UASP SATA III]"
But, I never went all the way and got the install set up with drivers for both systems. I think that would be the dream. Only one filesystem to think about.
I wonder if there’s some clever overlay way to plug the drive into my laptop, boot off that, have it copy everything over, then unplug the drive, work for a bit, and then have it automatically send it all back next time I plug the drive in…
say a ubuntu desktop, a macbook air and a windows laptop.
yeah file formats becomes a hinderance -- but they all can read exFAT at decent performance.