Le 29/07/2019 à 16:40, Qu Wenruo a écrit : > At least from what I see in this transid error, unless you ruled out the > possibility of bad disk firmware and LVM/LUKS, it's hard to say it's > btrfs causing the problem.
Well it would be such a coincidence that a machine that has been 100% stable since 2014 suddently crashes 2 filesystems on 2 different disks justy after upgrading to 5.2 and both things would be unrelated. Can happen, but the chances... > In fact, we have a more experienced sysadmin, Zygo, sharing his > experience of bad *HARDWARE* causing various Flush/FUA problem, which is > not easy to hit in normal use case, but only after power loss. > So for your transid error, it's really hard to pin down the cause, > unless you have deployed hundreds btrfs... For the record I am a professional sysadmin with 20+ years Linux experience and I have deployed BTRFS on dozens of systems (OK maybe not hundreds, not sure)... Kind regards. ॐ -- Swâmi Petaramesh <sw...@petaramesh.org> PGP 9076E32E
