Turning read-only is not exploding. What you are saying is that keeping to somehow work, like Ext4 and XFS would, letting bad memory chew through your data and FS structures, until the damage is so gr

(Quote)

Btrfs just helped catch the faulty memory. If you used Ext4/XFS, the error would have went unnoticed much longer, and corrupted your data or your filesystem without you knowing. So it is just &quo

(Quote)

(Quote)

(Quote)

to receive mail from Gmail, without any clear error as to why, just the appearance of silently dropped emails. Of course they blame me, inevitably, because they had no idea that MTA-STS was taken so

(Quote)

(Quote)

(Quote)

Reinstall debian 10, and BOOM, VPS can not access and restart/install etc, CPU MEM show "NaN%" and the VNC show "Irgendwas stimmt nicht Error ID:" (Image)

There is still good reason to use Btrfs or ZFS without ECC RAM. It is not going to be any worse than non-checksum filesystems, and it gives you an early warning that RAM is bad. People will ignore the

The roots of that stems from the paranoia that ZFS "scrub" might get confused by an error in non-ECC RAM, and do a "mis-recover" of data from parity, which would ac

(Quote)

What do you mean no error ? Is there no output at all ?

Well I spoke too soon, I tried changing the shebang to sh file on heirloom dir, it immediately spouting this error: benchy: syntax error at line 24:cred=$' unexpected`.

@Liso Not working on AlmaLinux release 8.7 (Stone Smilodon). No error either. Same with yabs.sh . bench.sh is working fine though.

(Quote)

I downloaded heirloom-sh-050706.tar.bz2 from this link, extract it and found bunch of *.c file and one makefile, I do make and it produce a executable named sh and symlink to it under the name jsh. I

grep error in logs > present_error.txt