On 2018年06月12日 00:42, Simon Kaiser wrote: >> On 2018年06月10日 09:56, Qu Wenruo wrote: >> >> Since there is no other csum error exposed by btrfs check/scrub, the fix >> for this particular csum item key bit flip can be fetched here: >> https://github.com/adam900710/btrfs-progs/tree/dirty_fix >> >> The usage will be (after the normal compile procedure) >> $ ./btrfs-corrupt-block -X <device> >> >> It needs to be executed offline (the <device> must be unmounted). >> >> Thanks, >> Qu >> > > Thank you very much, that fixed the issue :) > > btrfs scrub now shows 5 checksum errors on a single file > > [ 1869.456426] BTRFS warning (device sda5): checksum error at logical > 1271386112 on dev /dev/sda5, physical 1271386112, root 257, inode 8016535, > offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011 > 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal) > > > [ 1869.456429] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, > flush 0, corrupt 1, gen 0 > [ 1869.457975] BTRFS warning (device sda5): checksum error at logical > 1271390208 on dev /dev/sda5, physical 1271390208, root 257, inode 8016535, > offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011 > 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal) > > > [ 1869.457978] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, > flush 0, corrupt 2, gen 0 > [ 1869.459381] BTRFS warning (device sda5): checksum error at logical > 1271394304 on dev /dev/sda5, physical 1271394304, root 257, inode 8016535, > offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011 > 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal) > > > [ 1869.459383] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, > flush 0, corrupt 3, gen 0 > [ 1869.460827] BTRFS warning (device sda5): checksum error at logical > 1271398400 on dev /dev/sda5, physical 1271398400, root 257, inode 8016535, > offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011 > 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal) > > > [ 1869.460829] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, > flush 0, corrupt 4, gen 0 > [ 1869.462118] BTRFS warning (device sda5): checksum error at logical > 1271402496 on dev /dev/sda5, physical 1271402496, root 257, inode 8016535, > offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011 > 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal) > > > [ 1869.462120] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, > flush 0, corrupt 5, gen 0 > > I don't really need that file, can I simply delete it and forget about > it or is there something else I should do?
Of course you can delete it, and if nothing else went wrong, it should fix the problem. And of course, remove that offending memory stick. Thanks, Qu > > Yours, > Simon > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html >
signature.asc
Description: OpenPGP digital signature
