| raw e-mail | index | archive | help
Well, with this hack, the behavior looks to have changed to always fail leading-to an initial: *** [libzpool.so.2.full] Error code 1 The hack may disturb things too much and may not be sufficiently close to valid code for the context. Using -j1 got a first failure message: Failed assertion: p[i] =3D=3D 0 && which_base_extent_context =3D=3D = 0x22u That would be during ecache_alloc_grow. Still: *** [libzpool.so.2.full] Error code 1 =3D=3D=3D Mark Millard marklmi at yahoo.com