Okay sure, When I find free-time, will run few more combinations and let you know the details along with any other suggestions/thoughts on the interface. thanks. On 5/22/17, Qu Wenruo <quwenruo@xxxxxxxxxxxxxx> wrote: > Good to hear that. > > And you could try more combination (although I have done a lot during > the test) to see if it's good enough to be used as a better scrub > equivalent. > > And of course, any idea on the interface design (--offline under scrub > or other place) is welcomed. > > Thanks, > Qu > > At 05/22/2017 04:30 PM, Lakshmipathi.G wrote: >> Yes. It detects the injected corruption. >> >> #btrfs scrub start --offline /dev/loop6 >> ERROR: data at bytenr 145293312 mirror 0 csum mismatch, have >> 0x790f1fe1 expect 0xa30cb5c5 >> ERROR: full stripe 145227776 RECOVERABLE: Data stripes corrupted, but >> P/Q is good >> >> Scrub result: >> Tree bytes scrubbed: 131072 >> Tree extents scrubbed: 8 >> Data bytes scrubbed: 192512 >> Data extents scrubbed: 3 >> Data bytes without csum: 131072 >> Read error: 0 >> Verify error: 0 >> Csum error: 1 >> >> ---- >> Cheers, >> Lakshmipathi.G >> >> > > > -- ---- Cheers, Lakshmipathi.G http://www.giis.co.in http://www.webminal.org -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
