On Fri, Sep 27, 2013 at 04:22:16PM +0200, Tom Gundersen wrote:
Hi guys,
I have some questions about btrfs' handling of invalid csums.
For the sake of argument I'm assuming no raid or anything like that
(so only one copy exists of every file).
When I try to access a file whose csum does
On Fri, Sep 27, 2013 at 4:25 PM, Hugo Mills h...@carfax.org.uk wrote:
On Fri, Sep 27, 2013 at 04:22:16PM +0200, Tom Gundersen wrote:
1) What happens to the file. Will btrfs just leave it alone, or will
it be deleted from disk (I seem to remember reading this somewhere,
just want to confirm)?
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.
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,
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
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
