From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: data DUP
Date: Sat, 27 Apr 2013 16:29:38 -0700 [thread overview]
Message-ID: <klhn0u$vcr$1@ger.gmane.org> (raw)
In-Reply-To: <1367098836.14073.5.camel@ayu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 27/04/13 14:40, Calvin Walton wrote:
> Unfortunately, bugfixes in btrfs have tended to be *not* backported;
> aside from a few special cases, ...
Your efforts to scare me are admirable, but have failed :-)
As btrfs development has progressed, the probability of a random user like
me hitting bugs keeps decreasing. This is a reflection of the maturity of
the code base, the increasing number of users, improved test suites, more
eyes on the code, more diversity in uses etc. As far as I can see,
backported bugfixes are made when the probability of a bug being
encountered is significantly higher than the current probabilities, and
that is why they are rare.
As for the severity of the rarely hit bugs, the COW nature of the data
means there is unlikely to be corruption, and if there is then of the most
recent activity. Additionally the checksums mean it is possible to
proactively verify (online) that unexpected corruption hasn't been
creeping in.
And if all that fails, I have multiple layers of backups.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAlF8X14ACgkQmOOfHg372QT5EQCfSbzZBRdm1KyljpoNpP5kHy15
iFoAn2eyair54JQdhnL2dfvqAJrVMWe4
=9zYA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-27 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 20:17 data DUP Roger Binns
2013-04-20 20:48 ` Hugo Mills
2013-04-20 21:15 ` Roger Binns
2013-04-20 21:23 ` Hugo Mills
2013-04-20 23:01 ` Roger Binns
2013-04-27 21:40 ` Calvin Walton
2013-04-27 23:29 ` Roger Binns [this message]
2013-04-28 2:53 ` Alex Elsayed
2013-04-28 8:29 ` Roger Binns
2013-04-22 13:37 ` David Sterba
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='klhn0u$vcr$1@ger.gmane.org' \
--to=rogerb@rogerbinns.com \
--cc=linux-btrfs@vger.kernel.org \
/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.