There are consumer grade devices, where this is the most common failure mode. But usually a glitch in a video stream where these disks are typically used, isn't as critical as corrupting your bank account content (say, to the state prior to when you got your salary) :) (And that consumer grade devices usually never get a bug fix to address that). Richard Scheffenegger > -----Original Message----- > From: ietf-bounces@xxxxxxxx [mailto:ietf-bounces@xxxxxxxx] On Behalf Of > Christopher Morrow > Sent: Freitag, 15. März 2013 19:27 > To: Francis Galiegue > Cc: ietf@xxxxxxxx > Subject: Re: Is there a Git repository of RFCs? Or of Internet-Drafts? > > On Fri, Mar 15, 2013 at 2:15 PM, Francis Galiegue <fgaliegue@xxxxxxxxx> > wrote: > > On Fri, Mar 15, 2013 at 7:08 PM, Christopher Morrow > > <morrowc.lists@xxxxxxxxx> wrote: > > [....] > >>> > >>> What I mean is that if there is disk corruption on the server > >>> hosting the drafts (which can happen post write), rsync will happily > >>> send the checksum of the corrupted draft. Git's mechanism makes such > >>> a probability infinitesimal. > >> > >> wait, so.. if the disk fails things go bad... I'm confused. > >> > > > > If the disk goes bad so as to provoke a misread of a sector, post > > write, the file is effectively corrupted. If this happens with git, > > the checksum calculated on write will fail to match, and the > > corruption is detected. > > > > you seem to be protecting against a very, very, very uncommon failure... > I think you'd be better off protecting against a host of much more common > failure modes, eh?