On Sat, 10 Apr 1999, Greg Lehey wrote: ... > It looks like you have them now, but you didn't then.
Strange, I'm shure I haven't touched them. > > > The only fault where the misspelling of 'stripe' versus 'striped' in > > the configfile! > > That's not what your error messages are trying to tell you. That seems right. > ... > >>> S raid.p0.s0 State: stale PO: 0 B Size: 50 > >>> MB > >>> S raid.p0.s1 State: stale PO: 256 kB Size: 50 > >>> MB > >>> (Hmm, stale sigh. The vinum(8) GOTCHAS 2. is not explicit about my > >>> situation. > >> ... > > The panic occurs only, if I first use the incorrect config file with > > 'stripe', then the corrected one with 'striped' and then detaching > > the plex and the subdisks. This point is still valid. I just reproduced the panic again. This time the disks showed up and the errormessages where slightly different. They are not important for the panic. I did: )# vinum l Configuration summary Drives: 2 (4 configured) Volumes: 2 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D d1 State: up Device /dev/da1d Avail: 8664/8714 MB (99%) D d2 State: up Device /dev/da2d Avail: 8664/8714 MB (99%) V raid State: down Plexes: 1 Size: 100 MB P raid.p0 S State: down Subdisks: 2 Size: 100 MB S raid.p0.s0 State: stale PO: 0 B Size: 50 MB S raid.p0.s1 State: stale PO: 256 kB Size: 50 MB # vinum detach raid.p0 # vinum detach raid.p0.s0 # vinum detach raid.p0.s1 ..panic.. It seems to be important to remove the last stale subdisk. Bye! ---- Michael Reifenberger Plaut Software GmbH, R/3 Basis To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
