-----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----- -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
