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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

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

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, 
netbsd-bugs%NetBSD.org@localhost,
        tron%zhadum.org.uk@localhost
Subject: Re: kern/40569: Faild RAIDframe parity rewrite prevents system
        shutdown
Date: Tue, 10 Feb 2009 13:11:13 +0100

 On Mon, Feb 09, 2009 at 07:50:03PM +0000, Matthias Scheler wrote:
 >  On Sat, Feb 07, 2009 at 07:25:02PM +0000, Greg Oster wrote:
 >  >  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...
 >  
 >  1.) When I rebooted to install the new kernel the system managed to reboot
 >      despite the failed re-construction.
 >  
 >  2.) This is what I got when I attempted a re-construction with the
 >      new kernel:
 >  
 >  RECON: initiating reconstruction on col 0 -> spare at col 2
 >  wd3e: LBA48 bug reading fsbn 268435392 of 268435392-268435519 (wd3 bn 
 > 268435455; cn 266305 tn 0 sn 15), retrying
 >  wd3: soft error (corrected)
 >  wd2e: error writing fsbn 268435392 of 268435392-268435519 (wd2 bn 
 > 268435455; cn 266305 tn 0 sn 15), retrying
 >  wd2: (id not found)
 
 I don't understand why the problem is properly detected and worked around for
 wd3, but not for wd2 ? Are wd2 and wd3 identical devices ?
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --