I had a simple RAID1 system up and running for the first time yesterday on i386
3.8, but now after testing failure mode, I can't get things unwedged. It's
quite possible I wedged it worse while messing with it after the failure, so
I'm OK with starting the build over (no data yet) - but I can't
Dave Diller writes:
Here's what's been changed in the kernel not a lot. I don't understand why
it would panic on a simple reconstruct command.
I might be able to understand, but my crystal ball is at the
cleaners, and I can't guess what your panic message looked like, nor
what the
Oh... and from the obivous bugs department: In rf_openbsdkintf.c
case RAIDFRAME_GET_COMPONENT_LABEL:
there is a:
RF_Free( clabel, sizeof(RF_ComponentLabel_t));
missing before the:
return(EINVAL);
But that won't help with the problem your describing... (just noticed
the above as I
Dave Diller writes:
Oh... and from the obivous bugs department: In rf_openbsdkintf.c
case RAIDFRAME_GET_COMPONENT_LABEL:
there is a:
RF_Free( clabel, sizeof(RF_ComponentLabel_t));
missing before the:
return(EINVAL);
But that won't help with the problem your
started filing PR's for RAIDframe stuff in OpenBSD -- there have been
a lot of changes/fixes to RAIDframe in the last 5 years that aren't
I have $100 via Paypal for the person who commits RAID enabled boot
blocks for Sparc[64] and i386/amd64 on OpenBSD.
I have an $100 additional via Paypal
5 matches
Mail list logo
