Re: Blockbusting news, results are in

[ebiederm@xmission.com (Eric W. Biederman)]

Hans Reiser <reiser@namesys.com> writes:

> Larry McVoy wrote:
> 
> >
> >
> >I've told you guys over and over that you need to CRC the data in user
> >space, we do that in our backup scripts and it tells us when the drives
> >are going bad.  S
> >
> Why do the CRC in user space, that requires modifying every one of 7000+
> applications (if I understand you correctly, which is far from a sure thing;-)
> )?

End to end data integrity checking is a requirement.  Otherwise errors
happen silently and you rarely if ever see them.  And the error checking
must be end to end because you cannot trust the other layers to work
properly 100% of the time.

However to actually track down errors to root causes of errors, the closer
you can have your error checking to the hardware the better.  So having
CRC data or similar in the filesystem for both the metadata and the
file information is a good thing.

> Write a reiser4 CRC file plugin.  It would take a weekend, and most of the work
> would be cut and pasting from the default file plugin..  I understand why you do
> it in BK, but for user space as a whole user space is the wrong
> place.

Error checking should not be necessary for casual files that you don't
really care about but for times when you care about the integrity of
your data the application should be checking it.

Eric