Originally posted by arQon
View Post
Announcement
Collapse
No announcement yet.
The New NTFS Driver Looks Like It Will Finally Be Ready With Linux 5.15
Collapse
X
-
- Likes 2
-
Originally posted by kylew77 View PostSad to see the code GPLv2 with all the *BSD projects wanting to avoid any new GPL encumbered code.
- Likes 3
Comment
-
Originally posted by enigmaxg2 View PostSo, we can finally say goodbye to the atrocious CPU overhead and slowness of nfts-3g?
- Likes 1
Comment
-
Originally posted by pipe13 View PostI'm thinking either LVM/ext4 or btrfs. Is there any (dis)advantage to putting btrfs under LVM? This isn't cast in concrete yet -- would I maybe be best off KIS and just use lvm/ext4? For simplicity I'll want to use the same configuration on the big slow sdb drive, and any other sdd's I might acquire.
btrfs subvolumes don't really help here. They're great for doing snapshots though. I also like the compression features. I basically get 15% more storage for free. Also checksums mean I know when bitrot happens. In the worst case (like if you mount the same FS twice, either during hibernation in another OS, or in a VM with passed through disk access) you might get an unmountable FS that the repair tools only make worse. What works well however is btrfs-restore, which can read corrupted btrfs volume and dumps all the files with complete folder structure somewhere else. Why the repair tools are to bad when the restore tool can get everything back is a mystery. But that really only is an issue if you do something retarded like I did. Usually it's rock solid, even after unexpected power loss.
- Likes 1
Comment
-
-
Originally posted by Old Grouch View PostexFAT is lousy for file archiving.
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 1
Comment
-
Originally posted by kbios View Post
The data=journal mode absolutely protects from data loss
Code:data=journal All data are committed into the journal prior to being written into the main file system. Enabling this mode will disable delayed allocation and O_DIRECT support.
Last edited by birdie; 02 August 2021, 07:01 AM.
- Likes 1
Comment
Comment