From: Zoiled <zoiled@online.no>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: Hugo Mills <hugo@carfax.org.uk>, Waxhead <waxhead@online.no>,
linux-btrfs@vger.kernel.org
Subject: Re: Will BTRFS repair or restore data if corrupted?
Date: Thu, 26 Jan 2012 20:16:23 +0100 [thread overview]
Message-ID: <4F21A687.3010506@online.no> (raw)
In-Reply-To: <4F211DCF.90707@giantdisaster.de>
Stefan Behrens wrote:
> On 1/26/2012 9:59 AM, Hugo Mills wrote:
>> On Thu, Jan 26, 2012 at 12:27:57AM +0100, Waxhead wrote:
> [...]
>>> Will BTRFS try to repair the corrupt data or will it simply silently
>>> restore the data without the user knowing that a file has been
>>> "fixed"?
>> No, it'll just return the good copy and report the failure in the
>> system logs. If you want to fix the corrupt data, you need to use
>> scrub, which will check everything and fix blocks with failed
>> checksums.
> Since 3.2, btrfs rewrites the corrupt disk block (commit 4a54c8c and
> f4a8e65 from Jan Schmidt), even without scrub.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
So if I for example edit a text file three times and store it I can get
the following.
Version1: I currently like cheese
Version2: I currently like onions
Version3: I currently like apples
As far as I understand a disk corruption might result in me suddenly
liking onions (or even cheese) instead of apples without any warning
except in syslog.?! I really hope I have misunderstood the concept and
that there is some error correction codes somewhere.
next prev parent reply other threads:[~2012-01-26 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 23:27 Will BTRFS repair or restore data if corrupted? Waxhead
2012-01-26 7:19 ` Chester
2012-01-26 8:59 ` Hugo Mills
2012-01-26 9:33 ` Stefan Behrens
2012-01-26 19:16 ` Zoiled [this message]
2012-01-26 20:22 ` cwillu
2012-01-26 20:27 ` Zoiled
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F21A687.3010506@online.no \
--to=zoiled@online.no \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
--cc=waxhead@online.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.