🎉🎊 Breaking news, folks! Healthchecks.io has bravely decided to self-host their object storage like it's some kind of revolutionary act in 2026. 🚀 Good thing, too—in a world where everyone wants to hand over their data to the cloud, it's heartwarming to see someone reinstalling their hipster credentials with a #Btrfs #filesystem. 🙄✨
https://blog.healthchecks.io/2026/04/healthchecks-io-now-uses-self-hosted-object-storage/ #HealthchecksIO #SelfHosting #DataPrivacy #TechNews #HackerNews #ngated
Healthchecks.io Now Uses Self-hosted Object Storage

Healthchecks.io ping endpoints accept HTTP HEAD, GET, and POST request methods. When using HTTP POST, clients can include an arbitrary payload in the request body. Healthchecks.io stores the first 100kB of the request body. If the request body is tiny, Healthchecks.io stores it in the PostgreSQL database. Otherwise, it stores it in S3-compatible object storage. [...]

Healthchecks.io Blog
Microsoft Finally Ups FAT32 Size Limit

You probably don’t spend a lot of time using the FAT32 file system anymore, since it’s thoroughly been superseded many times over. Even so, Microsoft has seen fit to deliver an upgrade …

Hackaday
Microsoft Finally Ups FAT32 Size Limit

You probably don’t spend a lot of time using the FAT32 file system anymore, since it’s thoroughly been superseded many times over. Even so, Microsoft has seen fit to deliver an upgrade …

Hackaday

Linux 7.0 Released: Rust Gains Ground, XFS Gets Self-Healing, AI Tools Find Their Rules

Linux 7.0 officially released with Rust entering production use, XFS gaining self-healing capabilities, and AI coding tools getting formal governance in the kernel community.

https://yoota.it/en/linux-7-0-released-rust-gains-ground-xfs-gets-self-healing-ai-tools-find-their-rules/

Linux 7.0 è ufficiale: più spazio a Rust, novità per XFS e regole per gli strumenti AI

Linux 7.0 è stato rilasciato ufficialmente con Rust stabile, filesystem XFS auto-riparante e nuovo supporto hardware. Tutte le novità del kernel di aprile 2026.

https://yoota.it/linux-7-0-e-ufficiale-piu-spazio-a-rust-novita-per-xfs-e-regole-per-gli-strumenti-ai/

FTRS - is a Fault-Tolerant Radiation-Robust #Filesystem for #linux designed for use in #Space

Not happy with world domination alone, Linux is set out to conquer the universe!

https://lore.kernel.org/lkml/202604131[email protected]/

[RFC PATCH 0/10] ftrfs: Fault-Tolerant Radiation-Robust Filesystem - Aurelien DESBRIERES

Website backup crippled by 1.6MB Friends GIF that was replicated 246,173 times, breaking Linux's EXT4 filesystem limit — Jennifer Aniston's 'happy dance' animation ate up 377 gigabytes of data due to security policy

Admins were not happy. Initial attempts to resolve the issue by replacing files with hardlinks also failed due to ext4’s 65,000 hardlink limit.

Tom's Hardware
Website backup crippled by 1.6MB Friends GIF that was replicated 246,173 times, breaking Linux's EXT4 filesystem limit — Jennifer Aniston's 'happy dance' animation ate up 377 gigabytes of data due to security policy

Admins were not happy. Initial attempts to resolve the issue by replacing files with hardlinks also failed due to ext4’s 65,000 hardlink limit.

Tom's Hardware

New article: Btrfs 🌳

The Linux filesystem that never overwrites data. Every write goes to a new location.

Snapshots, RAID, per-block checksums with auto-repair on RAID, atomic transactions, all built into the filesystem.

https://internals-for-interns.com/posts/btrfs-filesystem/

#Linux #Btrfs #Filesystem

Btrfs | Internals for Interns

In the previous article , we explored XFS—a filesystem built for extreme scale that divides the disk into independent Allocation Groups, each with its own B+ trees for free space, inodes, and extent tracking. XFS, like every filesystem we’ve covered in this series, shares one fundamental characteristic with ext4, NTFS, and FAT32: it modifies data in place. When you update a block, the new data overwrites the old data at the same disk location.

Internals for Interns
Unix domain sockets operate differently from regular files. The permissions on the socket file itself determine access, so even if the directory is mounted as read-only (:ro), any process can still connect to the socket if it has the appropriate permissions
til #unix #filesystem