On Sep 27, 2013, at 1:13 PM, Zach Brown <z...@redhat.com> wrote: > On Fri, Sep 27, 2013 at 12:47:57PM -0600, Chris Murphy wrote: >> >> On Sep 27, 2013, at 11:51 AM, Zach Brown <z...@redhat.com> wrote: >> >>>>> 2) How may I tell btrfs to ignore all csums and just assume they are >>>>> all correct? The reason for wanting this is in case the csum is >>>>> garbled and the file is intact, or the csum is correct and the file is >>>>> only partially garbled, but may still contain useful data. >>>> >>>> You can't, right now. There's discussion on IRC about this very >>>> point right now. :) >>> >>> Well, hold on. Yes, you can't tell it to just not check checksums. >>> >>> But keep reading. It sounds like he thinks that *any* reads to the file >>> will error once any checksum has failed. Surely that's not true, you >>> can do use like dd conv=noerror and read all the extents of the file >>> whose checksums are still valid. >> >> Would that get me an identically sized copy of the file, such as it is? > > As far as I know, yes.
OK this part of what you said made my eyebrows raise: "read all the extents of the file whose checksums are still valid" because it implied that extents with invalid checksums aren't read. And that would be a much bigger problem than the original corruption. Chris Murphy-- 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
