On Sat, 10 Apr 1999, Greg Lehey wrote:
...
In fact, it's not necessary. It happens any time you detach the last
subdisk from a striped or RAID-5 plex.
Ups...
Correct. What happened to the stack traces? Don't bother, though,
I've reproduced it here. Expect a fix in a couple of hours.
Sorry,
Hi,
next try.
Please forgive if gets too stupid :-)
# cat x
drive d1 device /dev/da1d
drive d2 device /dev/da2d
volume raid
plex org stripe 256k
sd length 50m drive d1
sd length 50m drive d2
(please note again the misspelling of striped)
# vinum create x
1: drive d1 device /dev/da1d
** 1
On Friday, 9 April 1999 at 15:01:51 +0200, Michael Reifenberger wrote:
Hi,
next try.
Please forgive if gets too stupid :-)
# cat x
drive d1 device /dev/da1d
drive d2 device /dev/da2d
volume raid
plex org stripe 256k
sd length 50m drive d1
sd length 50m drive d2
(please note again
On Sat, 10 Apr 1999, Greg Lehey wrote:
...
You need to configure it. Use disklabel -e.
No, they where configured.
I have one ' d: 17848151 63 vinum' slice per drive.
The only fault where the misspelling of 'stripe' versus 'striped' in the
configfile!
...
Not much of anything,
[Format recovered--see http://www.lemis.com/email/email-format.html]
On Saturday, 10 April 1999 at 3:37:47 +0200, Michael Reifenberger wrote:
On Sat, 10 Apr 1999, Greg Lehey wrote:
...
You need to configure it. Use disklabel -e.
No, they where configured.
I have one ' d: 17848151 63
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.
On Saturday, 10 April 1999 at 4:05:10 +0200, Michael Reifenberger wrote:
On Sat, 10 Apr 1999, Greg Lehey wrote:
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
