The following is an excerpt from the 5.3.4R2 Start Here Guide - page 29. You can download the PDF file from the NOW site in the software download section.
========== start excerpt ============ Starting with 5.3.2, Data ONTAP checks the consistency of parity when performing disk scrubbing. If it detects parity inconsistency, the following events take place:
- A message is logged to /etc/messages indicating that there is parity inconsistency. When you see this message, it is important to call Technical Support for help in determining the root cause of the problem. - Data ONTAP enables block checksums to ensure data integrity. When checksums are enabled, there is some performance degradation.
If checksums are incorrect, Data ONTAP generates an error message similar to this one:
Checksum mismatch on disk 4.0, block 436964
A file named /etc/crash/parity_inconsistencies is created. It contains information about disk scrubbing, which helps Technical Support solve the parity inconsistency problem.
========= end excerpt ===============
I hope this helps.
Anissa
:-----Original Message----- :From: Jim Davis [mailto:jdavis@cs.arizona.edu] :Sent: Tuesday, January 11, 2000 9:21 AM :To: toasters@mathworks.com :Subject: checksum_blocks vol option? : : :Poking about now.netapp.com didn't turn up a lot of details about just :what this does -- or what sort of potential performance hit :there might be :when it's turned on. Is there a detailed discussion about :this somewhere, :or could someone in the know comment on it? Thanks! :