Le 30/07/2019 à 06:56, Qu Wenruo a écrit : >>> >>> I think I'me gonna emergency downgrade all my BTRFS machines to kernel >>> 5.1 before they break ,-( >> >> Full kernel message please. >> >> That commit is designed to corrupted inode item, we need more info to >> determine if it's a real corruption or not. >> >> Thanks, >> Qu > > Ping? If you really want to solve the problem, please provide the full > kernel message.
Hi, 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...) I don't have the « first kernel messages » for the SSD because I restored it to a backup before it failed, so obviously last kernel messages were lost. This morning if I try to scrub (using kernel5.1.16-arch1-1-ARCH) the external HD that failed yesterday, I get : BTRFS info (device dm-3): scrub: started on devid 1 BTRFS error (device dm-3): parent transid verify failed on 2137144377344 wanted 7684 found 7499 BTRFS error (device dm-3): parent transid verify failed on 2137144377344 wanted 7684 found 7499 BTRFS error (device dm-3): parent transid verify failed on 2137144377344 wanted 7684 found 7499 BTRFS: error (device dm-3) in btrfs_drop_snapshot:9603: errno=-5 IO failure BTRFS info (device dm-3): forced readonly BTRFS warning (device dm-3): failed setting block group ro: -30 BTRFS info (device dm-3): scrub: not finished on devid 1 with status: -30 Hope this helps... ॐ -- Swâmi Petaramesh <sw...@petaramesh.org> PGP 9076E32E
