On Sat, Jan 9, 2021 at 1:32 PM Sreyan Chakravarty <sreyan32@xxxxxxxxx> wrote: > > If I don't have ECC does that mean I shouldn't use BTRFS ? No. And also, this problem is not related to a memory error. In this case multiple writes from one commit are missing. They just didn't make it to stable media. There isn't enough information to know why. We might get lucky and find some clues in the systemd journal, before the file system went read only. What I can tell you is Btrfs doesn't have any known or suspected defects related to this kind of problem. It writes a superblock only once it has reason to believe the prior metadata writes were on stable media. There is also a write time tree checker designed to complain and go read only the moment there's an inconsistency when writing. This file system has a longer period of time of writes following the missing writes, which is also why the 'usebackup' root option didn't work. And the dropped writes also affect both copies of metadata. It's very unusual. Sreyan, is the drive that this file system is on the same drive as in this reported thread? https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/thread/DJWIOXUOSAAHAAXSUTKREV452QDCXV3D/#6UDYNNWOC23NJKSLMIABSAU4QFYANSRB -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
