Chris Murphy posted on Tue, 18 Feb 2014 11:48:49 -0700 as excerpted: >> This is not btrfs' fault but due to an hd error. I saw in the system >> logs >> btrfs: bdev /dev/sdb errs: wr 0, rd 2, flush 0, corrupt 0, gen 0 >> and a subsequent check on btrfs showed >> [/dev/sdb].write_io_errs 0 [/dev/sdb].read_io_errs 2 >> [/dev/sdb].flush_io_errs 0 [/dev/sdb].corruption_errs 0 >> [/dev/sdb].generation_errs 0 >> >> So, I have a read error on sdb. >>
It's worth noting that those errors don't reset automatically at boot or whatever. The idea is to give a sysadmin some idea how many errors have happened in the filesystem's lifetime or since the last manual reset. So as long as the number of errors isn't increasing at each boot, it's probably a historical and long since corrected error. btrfs device stats -z can be used to reset to zero if desired. See the btrfs (8) manpage. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
