Hi Qu, thanks for answering! >RO of the ext4, and still get corruption? Definitely looks like a >hardware problem to me. It's a weird error, because rebooting the machine the previous error disapears and the file could be read ok, then we know that the info in disk is ok. Then, the suspects list grows up: disk, RAM memory, kernel error (block layer?, filesystem layer?).... It's not a frequent bug so it's difficult to debug it. >For btrfs, as long as you're using data csum (default), btrfs can detect >such corruption. > >For v5.2 kernel, btrfs can even detects some easy to expose memory >corruption. > >But please keep in mind that, due to the fact btrfs (at least least >version) is very picky about corrupted on-disk data or memory, if you >find something wrong, you need to check dmesg to see what's going wrong. > >Furthermore, if your ssd is not reliable, especially when it lies about >FLUSH/FUA, btrfs can be easier to be corrupted, as btrfs completely >relies on FLUSH/FUA and metadata COW to ensure its safety against >powerloss, it's way easier to get corrupted if FLUSH/FUA is not >implemented corrected. > >(On the other hand, btrfs is more robust against data corruption, so as >long as your SSD is OK, you may find a better experience using btrfs) Then, it's advised to change the ext4 to btrfs or it's better to change the ISO packages filesytem to btrfs? Thanks! Jorge
