From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <30fef936405d9216f98c10a5c32b42ea@quanstro.net> From: erik quanstrom Date: Tue, 20 Jan 2009 09:19:04 -0500 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Changelogs & Patches? Topicbox-Message-UUID: 82ebf19a-ead4-11e9-9d60-3106f5b1d025 > > in the case of zfs, my claim is that since zfs can reuse blocks, two > > vdev backups, each with corruption or missing data in different places > > are pretty well useless. > > > Got it. However, I'm still not fully convinced there's a definite edge > one way or the other. Don't get me wrong: I'm not trying to defend > ZFS (I don't think it needs defending, anyway) but rather I'm trying > to test my mental model of how both work. if you end up rewriting a free block in zfs, there sure is. you can't decide which one is correct. > P.S. Oh, and in case of ZFS a damaged vdev will be detected (and > possibly re-silvered) under normal working conditions, while > fossil might not even notice a corruption. not true. one of many score checks: srv/lump.c:103: seterr(EStrange, "lookuplump returned bad score %V not %V", u->score, score); - erik