Re: kern/40569: Faild RAIDframe parity rewrite prevents system shutdown

[Greg Oster <oster%cs.usask.ca@localhost>]

The following reply was made to PR kern/40569; it has been noted by GNATS.

From: Greg Oster <oster%cs.usask.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/40569: Faild RAIDframe parity rewrite prevents system 
shutdown 
Date: Sat, 07 Feb 2009 13:23:33 -0600

 Matthias Scheler writes:
 > On Sat, Feb 07, 2009 at 06:55:01PM +0000, Greg Oster wrote:
 > >  Hmmmmm....  Around line 857 of src/sys/dev/raidframe/rf_reconstruct.c
 > >  there is a:
 > >  
 > >    return (1);
 > >  
 > >  You could try adding a printf() just before that line, and see if 
 > >  that gets printed....  I bet it doesn't... 
 > 
 > I'll make that change before I reboot the system the next time.
 
 K.. If I've caught you in time, please add a printf here:
 
  /* wait for writes to complete */
 
 in rf_reconstruct.c: rf_ContinueReconstructFailedDisk()
 and in that next while() loop, do something like:
 
    while (raidPtr->reconControl->pending_writes > 0) {
        printf("pending writes: %d\n",raidPtr->reconControl->pending_writes);
 
 to print the value of raidPtr->reconControl->pending_writes.
 
 I'd basicall like to know whether it thinks there have been write 
 errors at that point, and if not, then how many pending writes it's 
 waiting for...
 
 > >  wd3e: LBA48 bug reading fsbn 268435392 of 268435392-268435519 (wd3 bn 2684
 > 35455; cn 266305 tn 0 sn 15), retrying
 > >   wd3: soft error (corrected)
 > >   wd2e: error writing fsbn 268435392 of 268435392-268435519 (wd2 bn 2684354
 > 55; cn 266305 tn 0 sn 15), retrying
 > >   wd2: (id not found)
 > >  
 > >  What type of disks are these, and do they have the the 'LBA48-quirk' entry
 >  
 > >  to change addressing modes or whatever for block 268435455?
 > 
 > No, they apparently don't. But that's not the problem. The parity rewrite
 > worked in the past despite this bug. 
 
 Well... parity re-writes only read the disks and do writes if there 
 are errors... so if it didn't need to write to that block before, it 
 wouldn't have been detected...
 
 > And if I attempt to rebuild the
 > parity now one of the disks, probably wd2, produces really alarming
 > "clonk" noises. I think it is just a case of a broken disk.
 
 "clonk" noises from disks are never good :-}
 
 Later...
 
 Greg Oster