EXFat if you need cross compatibility, or just make an NFS/SMB server and have fun with the nightmare that is “why can’t I connect”
this post was submitted on 23 Nov 2023
1 points (100.0% liked)
Homelab
371 readers
9 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 11 months ago
MODERATORS
Which ntfs software are you using?
IIRC there are three options now (inc one in the kernel that's supposed to be a bit rough still) but the most stable seems to be the older fuse option of ntfs-3g.
I moved to getting none Linux boxes reading Ext4 drives using https://www.paragon-software.com/ drivers.
Have you tried using wsl mount on Windows to access Ext drives (may depend on your Windows version)...
Bit baffled by u/ajnozari comment on share security issues - SMB via SAMBA is well documented as to how to set things up...
Bit baffled by u/ajnozari comment on share security issues - SMB via SAMBA is well documented as to how to set things up...
Not sure they're referring to a security issue as much as sometimes SAMBA can be a bit cantankerous with with permissions and security in order to access ahare or that some users have problems with configuring it.
- you are literally force stopping writes to the disk...
I know, it's my own fault, but still, Windows seems to withstand it better?
NTFS is Windows' native filesystem. It writes to the USB much faster.
“This tree seems really sensitive, I ran a chainsaw through it and it just fell over???”
That's not exactly true. You may be stopping file transactions, but the filesystem handler code should still run until it has flushed its state, and if it doesn't, then that's a huge bug and isn't normal.
NTFS seems really sensitive?
no its not, NTFS ir rock solid, you are just using it incorrectly, use it with Windows as you are supposed to do..
I have had hundreds if not thousands of NTFS crashes and never lost a single file, but have lost quite a lot with other filesystems.
Not so much that NTFS is sensitive, rather it isn't prepared for a lot of corner cases it wasn't designed for. I'm curious of the need to share an NTFS volume via Samba that's also used with Windows... permissions alone could go to hell without careful thought about ACLs. If you really need to share a volume that's intended to be mounted in both Windows and Linux via Samba I'd go EXFAT if I didn't have an alternative to the whole situation.
Don’t use NTFS either Linux as 24/7 file system. Use Linux natives like ext4, xfs or zfs. And share the drive via samba. If it’s a drive that needs to travel between systems use EXFat.
Is this some dodgy USB dock problem rather than an NTFS problem?
You're using experimental drivers and force unmounting... And you actually have the gall to then try to pin the blame for errors from that on ntfs? Just no.
ntfs does have many issues which is why ms is developing refs to replace it. But stability or corruption isn't one of those issues. Ntfs is extremely solid in that regard due to the journaling.
Ntfs drivers in linux are however very buggy and generally considered experimental and that you should not write to ntfs drives if there's any data you care about as it could easily destroy all data there.
If you need a common writable data area then use exfat, not ntfs.
That's a good way to kill a disk. Don't use NTFS and you are fine. Go for Btrfs and similar.
I would not use NTFS.
Do the reverse. Use ZFS, Ext4, or Btrfs. Those are native Linux file systems.
Then you share the Linux folder with Windows over SMB, which is a Windows file sharing protocol that both Linux and Windows understand well. Voila, copy and paste between both machines without worrying about corruption.