Re: kern/44972: raidctl -R doesn't seem to work

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

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

From: Greg Oster <oster%cs.usask.ca@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/44972: raidctl -R doesn't seem to work
Date: Mon, 16 May 2011 16:10:33 -0600

 On Mon, 16 May 2011 22:05:04 +0000 (UTC)
 Greg Oster <oster%cs.usask.ca@localhost> wrote:
 
 > The following reply was made to PR kern/44972; it has been noted by
 > GNATS.
 > 
 > From: Greg Oster <oster%cs.usask.ca@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc: 
 > Subject: Re: kern/44972: raidctl -R doesn't seem to work
 > Date: Mon, 16 May 2011 16:04:13 -0600
 > 
 >  On Mon, 16 May 2011 22:00:01 +0000 (UTC)
 >  yamt%NetBSD.org@localhost wrote:
 >  
 >  > Could not verify parity
 >  > raid1: Error re-writing parity (1)!
 >  > wd3: mbr partition exceeds disk size
 >  > raid1: rebuilding: dk_lookup on device: /dev/dk1 failed: 16!
 >  
 >  Something(tm) didn't close /dev/dk1 properly, or /dev/dk1 was told to
 >  close, and didn't...   '-R' tells the device to close so the rebuild
 >  can (re-)open it again.  Something is amiss in there... 
 
 Hmm.. this is a non-autoconfigured set... so the call to
 rf_close_component() should be doing a vn_close() on the vp associated
 with /dev/dk1.
 
 Later...
 
 Greg Oster