On Wed, 5 May 1999 scw@seas.ucla.edu wrote:
On April 25 we got 3 raid scrub error messages. I called netapp (that morning) and the CE said that there was nothing to worry about unless they continue and/or there are hard disk errors associated with the problem. I expected that this was the case, and accepted this response.
What I got back was (in essence) don't worry, everything is fine and some canned (RAID for dummies) answers about why raid scrubbing is run and a brief synopsis of the error messages.
My story is different. NAC found some spurious errors like yours in one of my filer's logs. They called me and suggested that they want to run some diags with using DOT 5.2.1D7. I replied that indeed there were some errors, but they went away after I upgraded to 5.2.1P2. We came to conclusion that they should come over and run the diags anyway. They will do this on May 16 if the planets align correctly.
Please let me know if you find out more about this phenomenon. I think it is a bug of some sort in the older version of software rather than a hardware error. Here are the errors from my messages:
messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Inconsistent parity on volume vol0, RAID group 0, stripe #256159. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Rewriting bad parity block on volume vol0, RAID group 0, stripe #256159. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Inconsistent parity on volume vol0, RAID group 0, stripe #256160. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Rewriting bad parity block on volume vol0, RAID group 0, stripe #256160. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Inconsistent parity on volume vol0, RAID group 0, stripe #256161. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Rewriting bad parity block on volume vol0, RAID group 0, stripe #256161. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Inconsistent parity on volume vol0, RAID group 0, stripe #256162. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Rewriting bad parity block on volume vol0, RAID group 0, stripe #256162. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Inconsistent parity on volume vol0, RAID group 0, stripe #256163. messages.2:Sun Apr 11 01:59:01 CDT [raid_stripe_owner]: Rewriting bad parity block on volume vol0, RAID group 0, stripe #256163. messages.2:Sun Apr 11 04:59:40 CDT [consumer]: Scrub found 8 parity inconsistencies
Tom