On 7/30/19 9:21 AM, Qu Wenruo wrote: > >> I have emergency downgraded my system to 5.1 not to take any risk of >> crashing my SSD again (and if it crashes again anyway, then I will know >> it is not kernel 5.2's fault and let you know...) > That kernel message is to *prevent* any further damage, by rejecting any > invalid metadata. > If it caused mount failure, it shouldn't have written anything to the disk. > > The later transid error doesn't really match the original report. > > We really need the mount failure message of that fs.
This message is what I just got from my external backup USB HD that started acting up yesterday (before I reverted back to 5.1). I may find more in the syslog (but the machine is at home and I'm at work so it'll have to wait... I have the external disk with me however, so I would be able to run anything to test it now.) For the machine's system SSD, what happened is that mount never actually *failed* but the machine started displaying error messages at boot and these error messages went along with such BTRFS error messages on the console. For example the machines wouldn't boot to GUI anymore but I would still be able to log in in console and see that the log was crowded with failing services and BTRFS errors. Then I reformatted and reinstalled from backup, so the corresponding logs are indeed lost. ॐ -- Swâmi Petaramesh <sw...@petaramesh.org> PGP 9076E32E
