Jukka Salmi writes:
> Alistair Crooks --> current-users (2005-05-13 13:49:19 +0100):
> > On Fri, May 13, 2005 at 01:15:16PM +0200, Jukka Salmi wrote:
[smip]
> > > Eventually everything went fine; however, while reconstructing the disks
> > > I noticed a problem: the first time I reconstructed, the progress bar
> > > stalled at 29% and ETA constantly increased until reconstruction eventual
> ly
> > > succeeded. During the other two reconstructions, the progress bar always
> > > printed 0% and ETA 0:00 until it completed. However, reconstruction was
> > > always successful (AFAICT), and never took longer than expected.
> > > 
> > > What could be the source if this problem?
> > 
> > There were some 32-bit overflow problems with raidctl which Greg fixed
> > recently - I saw some 64 bit values were being returned properly, but
> > were being stored in 32 bit values.
> > 
> > 	http://mail-index.netbsd.org/source-changes/2005/05/01/0122.html
> 
> I used an up-to-date raidctl:
> 
> $ ident /sbin/raidctl                                                        
>   
> /sbin/raidctl:
>      $NetBSD: crt0.c,v 1.13 2003/07/26 19:24:27 salo Exp $
>      $NetBSD: rf_configure.c,v 1.22 2005/02/09 14:21:37 xtraeme Exp $
>      $NetBSD: raidctl.c,v 1.37 2005/05/01 22:37:34 oster Exp $
> 

Sounds like there is still a bug somewhere.. can you ship me 
(privately) the contents of 'raidctl -s' for all the RAID sets 
in question?  The output of 'disklabel wd0' and 'disklabel wd1'
might also be useful too.

Thanks.

Later...

Greg Oster