What do you do when NTFS fails you?
Reinstall then restore. Here the installation is on the metal of course just win10 running isolated & air gapped
#FileSystem
Today I learned the following. Journaling and journaling are two separate distinctly separate manners of keeping file systems in Sync.
When microsoft talks about journaling in NTFS you should never, ever think about the robust journaling system that Ext4 has
In comparison EXT4 journaling is a god while en NTFS journaling is not even an ant
I have EXT4 file systems connected to an extremely unstable machine. This thing crashes to green screens more than 64 times a day.
{It's a Gigabyte Mini PC in case you're interested never buy those. The machine came with overheating errors from the beginning. The factory installed a fan for the APU which is not even suitable for a GPU that was made a decade ago}
I've not even lost one bit of data on those EXT4 file systems.
Those NTFS file systems with journaling? I lost all of them. All NTFS file systems were lost
I didn't lose data because I have backups the file systems just keeled over simply because the machine kept rebooting
Thank you for being so robust EXT4
In POSIX, you can theoretically use inode zero
https://utcc.utoronto.ca/~cks/space/blog/unix/POSIXAllowsZeroInode
#HackerNews #POSIX #inode #zero #UNIX #filesystem #programming
Time to Change The Default Linux Filesystem (Ext4) With ??? | @djware
Understanding the Linux /usr Merge #filesystem #linux #unix #opensource
https://ostechnix.com/understanding-linux-usr-merge/
Linux 6.16 yields improved EXT4 performance!
As part of the changes that are done in Linux 6.16, there are some of the very interesting changes that are done to the EXT4 filesystem. Those changes yield improved performance, causing you to have a faster EXT4 filesystem compared to the recently released Linux 6.15.
Those changes have been made to improve the filesystem performance, which will be pushed to the v6.16 development branch from this PR, including:
- Fast commit performance improvements
- Multi-fsblock atomic write support for bigalloc file systems
- Large folio support for regular files
The large folio support for regular files was, in itself, a factor of the improvements, along with all other changes, which yielded over 37% performance increase according to the kernel test robot that made this report you can see here. According to the test robot, it has reported that it had noticed a 37.7% improvement on fsmark.files_per_sec.
The large folio support for regular files has been added with this patch, which checks for the following conditions in the ext4_should_enable_large_folio() function before enabling such support:
- If
i_modeon an inode is a regular file using theS_ISREG()macro - If either the data flags on the superblock or the inode flags has the journal data flags
- If the superblock has no verity and has no encryption support
Also, Linux 6.16 fixes some corruption bugs on an EXT4 file system caused by race conditions in the extent status tree. Those race conditions were potentially manifested from the heavy simultaneous allocation and deallocation to a single file.
Expect the first release candidate of Linux 6.16 in the next two weeks!
#EXT4 #Filesystem #Linux #Linux616 #LinuxKernel #news #Tech #Technology #update
#Linux Might Drop The #Apple #HFS / HFS+ #FileSystem Kernel Driver Support
#Apple no longer supports the Hierarchical File System on the latest versions of #macOS itself and in prior releases was read-only support since macOS 10.6 for HFS itself. The newer HFS+ file-system does continue to be supported by Apple. Linux support for HFS has been poor and ill-maintained and it looks like the kernel drivers could be on their way out.
https://www.phoronix.com/news/Linux-2025-Sad-State-HFS
Highlights from the main #erofs merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/79b98edf918e8146047e08817e2a42937428be02):
* a `fsoffset` mount option is introduced for file-backed mounts to specify the filesystem offset in order to adapt customized container formats.
* Intel QAT hardware accelerators are supported to improve DEFLATE decompression performance.
Highlights from the main #XFS merge for #Linux 6.16 (https://git.kernel.org/torvalds/c/f83fcb87f824b0bfbf1200590cc80f05e66488a7):
- Atomic writes for XFS
- Remove experimental warnings for pNFS, scrub and parent pointers
Highlights from the main #bcachefs merge for #Linux 6.16: https://git.kernel.org/torvalds/c/522544fc71c27b4b432386c7919f71ecc79a3bfb
- Incompatible features may now be enabled at runtime, via "opts/version_upgrade" in sysfs.
- Various changes to support deployable disk images
- Major error message improvements for btree node reads, data reads, and elsewhere.
- New option, 'rebalance_on_ac_only'.
- Repair/self healing:
- We can now kick off recovery passes and run them in the background if we detect errors.
- Performance:
- Faster snapshot deletion
- Faster device removal
- We're now coalescing redundant accounting updates prior to transaction commit, taking some pressure off the journal.
- Stack usage improvements: All allocator state has been moved off the stack
"some performance improvements and one minor mount option update" are among the main #Btrfs changes merged for #Linux 6.16:
https://git.kernel.org/torvalds/c/5e82ed5ca4b510e0ff53af1e12e94e6aa1fe5a93
A few highlights:
Performance:
- extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime)
- extent io tree cleanups lead to performance improvements by avoiding unnecessary searches or repeated searches
- more efficient extent unpinning when committing transaction (estimated run time improvement 3-5%)
User visible changes:
- remove standalone mount option 'nologreplay', deprecated in 5.9, replacement is 'rescue=nologreplay'
- in scrub, update reporting, add back device stats message after detected errors (accidentally removed during recent refactoring)
Core:
- convert extent buffer radix tree to xarray
- continued preparations for large folios
💡 Kernel Linux 6.15: driver Rust, exFAT veloce e supporto ampliato
https://gomoot.com/kernel-linux-6-15-driver-rust-exfat-veloce-e-supporto-ampliato/
#arm #blog #driver #filesystem #kernel #linux6.15 #news #nova #opensource #picks #rust #tech #tecnologia
The btrfs filesystem is now faster on Linux 6.16!
#Linux #Kernel #LinuxKernel #Computers #Laptops #TechNews #TechUpdates #btrfs #filesystem
https://officialaptivi.wordpress.com/2025/05/25/linux-6-16-will-see-more-btrfs-improvements/
Linux 6.16 will see more btrfs improvements
The btrfs filesystem in Linux 6.16 has undergone many improvements that make its performance faster than before. It has already been improved across Linux releases, but the upcoming version of Linux sees even more improvements to this filesystem. Any system that uses this filesystem can now benefit from those improvements.
The buffer conversion work underwent some throughput and runtime improvements for metadata heavy operations, backed by several commits in a pull request made to the 6.16 branch, such as “extent buffer conversion to xarray gains throughput and runtime improvements on metadata heavy operations doing writeback (sample test shows +50% throughput, -33% runtime).”
The tree cleanups have been improved to avoid repeated or unnecessary searches. This improves the I/O performance, should any operation rely on tree cleanups. As for committing transactions, the extent unpinning action has become more efficient than before, yielding a 3-5% performance improvement in runtime.
You can find more about this pull request by clicking on the below button:
Learn more#Btrfs #Filesystem #Linux #LinuxKernel #news #Tech #Technology #update
Installed Program only runs from Folder - 'Cannot load key names.' #filesystem #paths #executable #alias
Unlike normal operating systems that let you access the filesystem directly by its path (/home/zlendy/..., /Users/zlendy/..., C:\Users\zlendy\...), Android forces you to use weird intents and URLs just to open a file.
I get that its for security and whatever but I still find it extremely annoying.
#androiddev #filesystem #rant
With keen interest I studied the following blogpost by @stefano
You have to read the blog post carefully, if necessary, read it twice, because there are things said between the words and the lines that should resonate with you
One major lesson is extremely important know when to cut and leave; never ever deviate from your course afterwards
When politics, corruption and deviousness are involved, you have to make absolutely certain that both your integrity and your health remain at your primary interest
A lot has been learned by me from this article
Thank you for sharing it with us Stefano
https://it-notes.dragas.net/2025/05/21/the_day_glusterfs_tried_to_kill_my_career/
#IT_Notes #NotesFromTheCrypt #LessonsLearned #OpenSource #programming #filesystem #POSIX
how do i navigate programs/packages? Where is my program? #softwareinstallation #2404 #filesystem
how do i navigate programs/packages? Where is my program? #2404 #filesystem #gui #interface
I just swapped out the #filesystem out from under my current #Linux installation on my laptop
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst