comment, and effectively remove, a DIAGNOSTIC check that

is invalid for RAID5_RS.
This commit is contained in:
oster 2012-02-20 22:42:05 +00:00
parent c1d02dab7b
commit e8dd466041
1 changed files with 10 additions and 2 deletions

View File

@ -1,4 +1,4 @@
/* $NetBSD: rf_reconmap.c,v 1.33 2011/08/31 18:31:02 plunky Exp $ */
/* $NetBSD: rf_reconmap.c,v 1.34 2012/02/20 22:42:05 oster Exp $ */
/*
* Copyright (c) 1995 Carnegie-Mellon University.
* All rights reserved.
@ -34,7 +34,7 @@
*************************************************************************/
#include <sys/cdefs.h>
__KERNEL_RCSID(0, "$NetBSD: rf_reconmap.c,v 1.33 2011/08/31 18:31:02 plunky Exp $");
__KERNEL_RCSID(0, "$NetBSD: rf_reconmap.c,v 1.34 2012/02/20 22:42:05 oster Exp $");
#include "rf_raid.h"
#include <sys/time.h>
@ -157,7 +157,14 @@ rf_ReconMapUpdate(RF_Raid_t *raidPtr, RF_ReconMap_t *mapPtr,
/* do we need to move the queue? */
while (i > mapPtr->high_ru) {
#if 0
#ifdef DIAGNOSTIC
/* XXX: The check below is not valid for
* RAID5_RS. It is valid for RAID 1 and RAID 5.
* The issue is that we can easily have
* RU_NOTHING entries here too, and those are
* quite correct.
*/
if (mapPtr->status[mapPtr->head]!=RU_ALL) {
printf("\nraid%d: reconmap incorrect -- working on i %" PRIu64 "\n",
raidPtr->raidid, i);
@ -169,6 +176,7 @@ rf_ReconMapUpdate(RF_Raid_t *raidPtr, RF_ReconMap_t *mapPtr,
panic("reconmap incorrect");
}
#endif
#endif
mapPtr->low_ru++;
mapPtr->high_ru++;