On Thu, Jan 24, 2019 at 11:04:47AM +0800, Qu Wenruo wrote: > > > On 2019/1/24 上午1:16, David Sterba wrote: > > On Fri, Jan 18, 2019 at 10:19:51AM +0800, Qu Wenruo wrote: > >> Patchset can be fetched from github: > >> https://github.com/adam900710/linux/tree/write_time_tree_checker > >> Which is based on v5.0-rc1 tag. > >> > >> This patchset has the following two features: > >> - Tree block validation output enhancement > >> * Output validation failure timing (write time or read time) > >> * Always output tree block level/key mismatch error message > >> This part is already submitted and reviewed. > >> > >> - Write time tree block validation check > >> To catch memory corruption either from hardware or kernel. > >> Example output would be: > >> > >> BTRFS critical (device dm-3): corrupt leaf: root=2 block=1350630375424 slot=68, bad key order, prev (10510212874240 169 0) current (1714119868416 169 0) > >> BTRFS error (device dm-3): write time tree block corruption detected > >> BTRFS critical (device dm-3): corrupt leaf: root=2 block=1350630375424 slot=68, bad key order, prev (10510212874240 169 0) current (1714119868416 169 0) > >> BTRFS error (device dm-3): write time tree block corruption detected > >> BTRFS: error (device dm-3) in btrfs_commit_transaction:2220: errno=-5 IO failure (Error while writing out transaction) > >> BTRFS info (device dm-3): forced readonly > >> BTRFS warning (device dm-3): Skipping commit of aborted transaction. > >> BTRFS: error (device dm-3) in cleanup_transaction:1839: errno=-5 IO failure > >> BTRFS info (device dm-3): delayed_refs has NO entry > > > > Two tests complain: > > Any info about the reproducibility and VM/hardware info? Especially for > the VM ram size. 2G ram with 4 cpus, this was first run of the patchset so I can't say how reliable it is yet.
