{"slug": "this-newly-proposed-linux-filesystem-can-fix-corrupted-data", "title": "This Newly Proposed Linux Filesystem Can Fix Corrupted Data", "summary": "Aurelien Desbrieres submitted an 18-patch RFC to the Linux kernel filesystem mailing list for BeamFS, a filesystem that stores Reed-Solomon error-correcting codes in every block to correct small data corruption on read instead of relying on a spare copy like Btrfs and ZFS. Desbrieres wrote the code, the patch-checking tool and the cover letter with Anthropic's Claude, tagging each patch with the kernel's required `Assisted-by` disclosure, and is seeking feedback rather than a merge, asking maintainers whether BeamFS should be a separate filesystem and whether a journal must precede further review. In his Zenodo technical report, ext4 and ext3 returned wrong data without error while Btrfs refused the read, and BeamFS returned the correct file every time except once, when a bit flip hit a pointer to the file's data and it refused the read; the tests simulated damage by flipping single bits on virtual machines and USB flash drives, not in a real radiation environment, and the README warns against trusting the code with anything important.", "body_md": "The kernel's filesystem mailing list has received an 18-patch proposal this week from [Aurelien Desbrieres](https://github.com/roastercode?ref=itsfoss.com), the creator of [BeamFS](https://github.com/roastercode/beamfs?ref=itsfoss.com). It takes the place of FTRFS, an earlier filesystem he had proposed back in April.\n\nAurelien says he used Anthropic's Claude to write the code, the tool that checks the patches, and [the cover letter](https://lore.kernel.org/lkml/20261019041728.327785-1-aurelien@hackers.camp/?ref=itsfoss.com).\n\nHe also points out that every patch carries an `Assisted-by` tag. You might remember that is the disclosure the kernel's [AI coding assistants policy](https://itsfoss.com/news/linux-ai-coding-assistants-policy/) asks for. The same policy keeps the human submitter responsible for the code.\n\n## How does it fix data?\n\nFilesystems that can repair damage, like *Btrfs* and *ZFS*, usually do it by falling back on a spare copy of the data. BeamFS skips that and stores [Reed-Solomon](https://en.wikipedia.org/wiki/Reed%E2%80%93Solomon_error_correction?ref=itsfoss.com) error-correcting codes inside every block.\n\nEvery read gets checked against those codes, and small amounts of damage are corrected before the data reaches the application. If the filesystem can tell the damage is beyond repair, the read fails with an error instead of returning the wrong bytes.\n\nThe idea started with satellite computers. They keep data on a single drive and cannot fit a second copy. The same case is made for radiotherapy rooms.\n\n[Neutrons](https://www.britannica.com/science/neutron?ref=itsfoss.com) from treatment machines can flip bits in the computers there, including the ones handling imaging and records. Aurelien argues a silently wrong byte does more damage in that setting than a failed read.\n\n**BeamFS has not been tested in a real radiation environment yet**. The tests done so far simulated the damage by flipping single bits in data as it was read on virtual machines and USB flash drives.\n\nIn his [technical report](https://zenodo.org/records/23253350?ref=itsfoss.com), *ext4* and *ext3* returned wrong data without any error, while *Btrfs* refused to read the file. BeamFS returned the correct file every time except once, when a flip hit a pointer to the file’s data and it refused the read.\n\nDo keep in mind that the comparison is uneven. Each filesystem received a different number of flips, and the report makes it clear that **it is not a ranking**.\n\n## Is it close to landing?\n\nNope, this is a request for comments (RFC). Aurelien is asking for feedback, not calling for a merge, and he has two questions for the maintainers.\n\nThe first is whether it should be a separate filesystem or be proposed for an existing one.\n\nThe second is the journal, the log other filesystems use to recover from crashes. BeamFS lacks one and relies on its `fsck` tool after an unclean shutdown. Aurelien asks whether it has to come before further review or can be submitted afterward.\n\nSo far, the only reply [in the thread](https://lore.kernel.org/lkml/4ebbbb17-7833-4a2c-9e7e-b3c731873caf@infradead.org/?ref=itsfoss.com) is about where the `MAINTAINERS` entry sits alphabetically.\n\nThe project's [README](https://github.com/roastercode/beamfs/blob/main/README.md?ref=itsfoss.com) has a warning of its own. It lists bugs that can lose data, open security holes, and crash the kernel, **advising against trusting the code with anything important**.\n\nEnjoyed this update? Support independent Linux news coverage\n\nIt's FOSS has been helping people use Linux for the past 14 years. Help us stay independent from big tech. Become a Plus member, enjoy ad-free reading and get 5 eBooks.\n\nSkip the AI slop and SEO spam in your Google results\n\nTell Google you prefer It's FOSS, and it will show our Linux news and tutorials, created by experienced Linux users, more often when you search. It takes just a click.\n\n[Set as preferred source](https://www.google.com/preferences/source?q=itsfoss.com)\n\nGet FOSS Weekly in your inbox", "url": "https://wpnews.pro/news/this-newly-proposed-linux-filesystem-can-fix-corrupted-data", "canonical_source": "https://itsfoss.com/news/beamfs-linux-filesystem-proposal/", "published_at": "2026-10-22 14:39:35+00:00", "updated_at": "2026-10-25 17:11:32.878654+00:00", "lang": "en", "topics": ["artificial-intelligence", "ai-tools", "developer-tools"], "entities": ["Aurelien Desbrieres", "BeamFS", "Anthropic", "Claude", "Linux kernel", "Btrfs", "ZFS", "ext4"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/this-newly-proposed-linux-filesystem-can-fix-corrupted-data", "markdown": "https://wpnews.pro/news/this-newly-proposed-linux-filesystem-can-fix-corrupted-data.md", "text": "https://wpnews.pro/news/this-newly-proposed-linux-filesystem-can-fix-corrupted-data.txt", "jsonld": "https://wpnews.pro/news/this-newly-proposed-linux-filesystem-can-fix-corrupted-data.jsonld"}}