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 not match, btrfs logs an > error and refuses access to the file. I have two questions about this: > > 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)? It's left there. > 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. :) Hugo. -- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk === PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- A clear conscience. Where did you get this taste --- for luxuries, Bernard?
Attachment:
signature.asc
Description: Digital signature
