Hi! The graid5 female testing officer found, that this problem just happens with EFF aka. TNG... with the stable version this problem doesnt occur... I dont know why, since both use the same destroy aka. stop procedure... Bye Arne --- Henrik Bergkvist <henrik_at_mdfnet.se> wrote: > Arne Wörner wrote: > > --- Henrik Bergkvist <henrik_at_mdfnet.se> wrote: > > > >> I took a picture. You can see it here: > >> http://mds.mdh.se/~kem96hbt/panic.jpg > >> > >> > > Hmm... > > U could increase debug level to 10 or so (sysctl kern.geom.raid5.debug=10) > > before u do that "graid5 stop" command again... Then u can see better, why > > graid5 couldnt stop... > > > > Currently it looks like GEOM (g_event) gets an event, that is somehow bad, > > which is not necessarily a graid5 bug... In R6.2 the stop cmd worked fine > in > > some version of graid5 (I dont remember which, because I personally never > > really needed to stop a device)... > > > > -Arne > > > That gave the exact same error. > > /Henrik > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.comReceived on Mon Nov 12 2007 - 17:39:18 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:21 UTC
