{"id":183926,"date":"2026-10-21T17:40:46","date_gmt":"2026-10-21T15:40:49","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/dlya-yadra-linux-realizovany-novye-fajlovye-sistemy-beamfs-xmfs-i-meshxfs"},"modified":"2026-10-21T17:40:54","modified_gmt":"2026-10-21T15:40:54","slug":"new-beamfs-xmfs-and-meshxfs-file-systems-implemented-for-the-linux-kernel","status":"publish","type":"post","link":"https:\/\/prohoster.info\/hu\/blog\/news\/new-beamfs-xmfs-and-meshxfs-file-systems-implemented-for-the-linux-kernel","title":{"rendered":"A Linux kernelhez \u00faj f\u00e1jlrendszerek val\u00f3sultak meg: BeamFS, XMFS \u00e9s MeshXFS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

A Linux kernel developers Mailing List has published patches for the implementation of the BeamFS file system, which utilizes Reed-Solomon encoding to identify and recover corrupted data in configurations with a single drive. The main areas of application for BeamFS include onboard computers of satellites, equipment in radiation therapy rooms, and other systems operating in high-radiation conditions, where recovering distorted data is more critical than the inability to read the information.<\/p>\n

By default, BeamFS can restore up to 8 lost bytes in each 255-byte block with an overhead of 7% (288 bytes of recovery codes for every 4096 bytes of stored data). Error correction codes are applied not only to data but also to metadata in the superblock, inode, directory indexes, and bitmaps. Integrity checks and attempts to recover missing data are performed with every read operation. If data integrity cannot be guaranteed, the operation ends with an error '-EIO', thereby excluding the hidden return of corrupted data. <\/p>\n

Experiments have shown that, when irradiating the i.MX 8M Plus board with Linux and ext4 FS with protons with energies from 20 to 58 MeV, 90% of all failures occurred at the file system and storage device driver levels. A simulation of single-bit distortions when reading from storage was also conducted: BeamFS and Btrfs successfully detected data corruption and always returned an error, while ext4 and ext3 silently returned corrupted data.<\/p>\n

BeamFS ensures integrity and recovery only from the stage of reading from the physical medium to passing to the page cache in RAM. Integrity in RAM can be maintained using error-correcting memory chips.
\nOne limitation of BeamFS is the absence of logging support and the Copy-on-Write (CoW) mode \u2014 metadata is written to the drive in an unordered manner, requiring a full check with fsck in case of an improper shutdown.<\/p>\n

In addition to BeamFS, two other file systems have recently been proposed for the Linux kernel: <\/p>\n