On Thu, Dec 31, 2015 at 1:24 PM, Hugo Mills <[email protected]> wrote: > On Thu, Dec 31, 2015 at 01:11:25PM -0700, Chris Murphy wrote: >> This is a torture test, no data is at risk. >> >> Two devices, btrfs raid1 with some stuff on them. >> Copy from that array, elsewhere. >> During copy, yank the active device. >> >> dmesg shows many of these: >> >> [ 7179.373245] BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr >> 652123, rd 697237, flush 0, corrupt 0, gen 0 >> >> Why are the write errors nearly as high as the read errors, when there >> is only a copy from this device happening? > > I'm guessing completely here, but maybe it's trying to write > corrected data to sdc1, because the original read failed? >
Egads. OK that makes sense. -- Chris Murphy -- 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
