Kazushi Marukawa writes:
> Hi,
> 
> This time I made a backup of my RAID5 and tested it to
> reproduce a crash caused by RAIDframe which I told in my old
> mail.  I could reproduce it with clean file system.  So, I
> guess RAIDframe has some problem in unconfigure or configure
> section.  Please check them if it's possible.  Thanks.
> 
> I used Aug 17 or 18's kernel.  So, this problem may be
> already fixed, though.  Indeed, I experienced strange lock
> up problem with this kernel which is already solved in
> today's kernel.
> 
> 
> What I did is basically to unconfigure an exist raid
> partition and reconfigure it from scratch.  Actual commands
> what I executed are:
> 
>  $ raidctl -u raid0
>  $ raidctl -C raid0.conf raid0
>  $ raidctl -I xxxxxx raid0
>  $ raidctl -i raid0
>  $ disklabel -w raid0 labelXXX

What does this 'labelXXX' look like?  Alternately, what does 'disklabel raid0' 
say?

>  $ newfs raid0
>  $ mount /dev/raid0e /mnt
>  $ cd usr
>  $ tar cf - . | (cd /mnt; tar xfp -)
>  uvm_fault(0xc06015a0, 0x0, 0, 1) -> e
>  kernel: page fault trap, code=0
>  Stopped in pid 245 (raid) at    VOP_STRATEGY+0x1f:      movl          0x3c(%
> eax),%eax
>  db> trace
> VOP_STRATEGY(c0c8a15c,c0c6a8e4,c0bc0700,3fff10b9,6280) at VOP_STRATEGY+0x1f
> rf_DispatchKernelIO(c0c6a8e4,c0bc0700,c0c65750,c0ba3980,c0bc2000) at rf_DispatchKernelIO+0x1ca

Hmmmm.

Later...

Greg Oster