[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: raidframe oddity, take three (kernel panic!)
der Mouse writes:
> >> If so, then raidframe won't work with such large disks. You need
> >> [...] rf_reconstruct.c 220.127.116.11 or later.
> > 4.0.1 seems to use 1.95.2.something, so I'll probably just push the
> > machine to 4.0.1. Thank you very much!
> Now done. Doesn't help.
> And yes, I've gone to some lengths to verify that the kernel that just
> now crashed is indeed the one I built an hour or two ago from the 4.0.1
> source tree (which means, with rf_reconstruct.c,v 18.104.22.168).
Hmm.. 22.214.171.124 isn't sufficient..
> Or is 126.96.36.199 _not_ later than 188.8.131.52? I don't totally understand
> CVS numbering.
I could have sworn that 184.108.40.206 was in 4.0.1, but maybe I'm thinking
of 4.1?? Regardless, what you want is version 220.127.116.11 of rf_reconstruct.c
and the associated changes that go with them:
cvs rdiff -r1.29 -r18.104.22.168 src/sys/dev/raidframe/rf_reconmap.c
cvs rdiff -r1.10 -r22.214.171.124 src/sys/dev/raidframe/rf_reconmap.h
cvs rdiff -r126.96.36.199 -r188.8.131.52 src/sys/dev/raidframe/rf_reconstruct.c
cvs rdiff -r1.22 -r184.108.40.206 src/sys/dev/raidframe/rf_reconstruct.h
cvs rdiff -r1.24 -r220.127.116.11 src/sys/dev/raidframe/rf_revent.c
as mentioned here:
Main Index |
Thread Index |