Originally posted by jarekZ
View Post
Announcement
Collapse
No announcement yet.
The New NTFS Driver Looks Like It Will Finally Be Ready With Linux 5.15
Collapse
X
-
Last edited by Slartifartblast; 31 July 2021, 05:52 PM.
- Likes 3
-
Originally posted by birdie View Post
exFAT is (good) for removable storage and file archiving. It can't and won't work for storing anything which requires MAC, so NTFS is as relevant as ever.
The problem is that ext(x) filesystems allow any character in a filename except for NULL and forward slash, which is a superset of the allowed characters in the exFAT definition:
For example: Asterisk; Less-than sign; Greater-than sign; Colon; Question mark; Vertical bar; and Back slash are not allowed in exFAT filenames (plus sundry control codes)
I've been caught out by this and had to rename a non-trivial number of files.
Similar restrictions apply to NTFS: https://docs.microsoft.com/en-us/win.../naming-a-file - note that if NTFS uses the POSIX namespace any Unicode character except / and Null are is allowed. Note that the POSIX standard for portable filenames is considerably more restrictive.
Non-Microsoft drivers can put non-standard characters in filenames used in exFAT, but obviously this will generate undefined behaviour if accessed by a Microsoft driver, or one written to abide by the Microsoft specification.
I'm not going to hold up the relatively liberal approach of many Linux filesystems towards filename standards as being perfect. It is subject to well argued criticisms: https://dwheeler.com/essays/fixing-u...filenames.html
I'm still looking for a good cross-platform approach for file archiving. exFAT isn't the solution, and neither, unfortunately, is UDF (in any of its revisions), which is a shame.
- Likes 4
Leave a comment:
-
Originally posted by xeekei View Postbut damn Android has to do weird shit and ONLY allows storage it has formatted itself? Why can't phones be normal...
- Likes 2
Leave a comment:
-
This is great news.
And on exFAT, I'm using it between Linux and Windows, but damn Android has to do weird shit and ONLY allows storage it has formatted itself? Why can't phones be normal...
- Likes 2
Leave a comment:
-
Originally posted by pipe13 View PostGiven exFAT has advantages over FAT, in what ways does it or can it replace NTFS? I've always (perhaps mistakenly) thought all the FATs were somewhat toys compared to journaling filesystems such as NTFS, EXT4, HFS, and their ilk. (And where does f2fs fit in?) My question is what use cases do Paragon's paying customers have that previously required NTFS but now can at least get by with exFAT, use cases that with earlier FATs could not?
- Likes 2
Leave a comment:
-
Originally posted by birdie View Post
(ext4) journalling does not protect you from data loss - it only makes fsck run faster and in a perfect world you must always run fsck even if you have journalling but your system crashed for some reasons.
- Likes 5
Leave a comment:
-
Originally posted by pipe13 View Post
I agree. In that regard I've a question about Michaels final dig: "but these days NTFS is of declining relevance to companies now focused on exFAT and other file-system options, which has led [Paragon] to be open to upstreaming their code."
Given exFAT has advantages over FAT, in what ways does it or can it replace NTFS? I've always (perhaps mistakenly) thought all the FATs were somewhat toys compared to journaling filesystems such as NTFS, EXT4, HFS, and their ilk. (And where does f2fs fit in?) My question is what use cases do Paragon's paying customers have that previously required NTFS but now can at least get by with exFAT, use cases that with earlier FATs could not?
For the record, I'm really looking forward to Paragon's new NTFS3 for my own development and testing efforts split between Windows and Linux. I'm using ntfs-3g on a shared SDD, but have had to duplicate much of my effort onto a linux-only ext4 partition simply because fuse is too slow.
- Likes 3
Leave a comment:
-
Originally posted by kbios View Post
I hope you have a robust backup system
- Likes 4
Leave a comment:
Leave a comment: