BeamFS creator Aurelien Desbrieres is not calling for a merge, but is requesting feedback on an 18-patch proposal that takes the place of FTRFS, an earlier filesystem he proposed in April. The Linux/Open Source blog It's FOSS reports: Filesystems 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 error-correcting codes inside every block. Every 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... In his technical report, 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. "Aurelien says he used Anthropic's Claude to write the code, the tool that checks the patches, and the cover letter..." Read more of this story at Slashdot.
A Newly Proposed Linux Filesystem Can Fix Corrupted Data
Aurelien Desbrieres has posted an 18-patch proposal for BeamFS, a new Linux filesystem that stores Reed-Solomon error-correcting codes inside every block and corrects small amounts of damage on each read, replacing his earlier FTRFS proposal from April. In Desbrieres' technical report, ext4 and ext3 returned wrong data without any error and Btrfs refused to read the file, while BeamFS returned the correct file in every test except one, when a flip hit a pointer to the file's data and it refused the read. Desbrieres, who is not calling for a merge and is requesting feedback, said he used Anthropic's Claude to write the code, the patch-checking tool and the cover letter.
Run your AI side-project on zahid.host
EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.