Re: Panic: Invalid longjmp with vinum configured by novice

1999-04-09 Thread Greg Lehey
On Friday,  9 April 1999 at 21:59:57 +0200, Michael Reifenberger wrote:
> On Fri, 9 Apr 1999, Jacques Vidrine wrote:
>
>> Date: Fri, 09 Apr 1999 12:30:41 -0500
>> From: Jacques Vidrine 
>> To: Michael Reifenberger 
>> Cc: Greg Lehey , FreeBSD-Current 
>> Subject: Re: Panic: Invalid longjmp with vinum configured by novice
>>
>> On 9 April 1999 at 11:31, Michael Reifenberger  wrote:
>> [snip]
>>>> But vinum(8) doesn't offer
>>>> you much in the way of editing facilities either.
>>> A command history and commandline editing :-)
>>
>> Use ile in ports/misc/lile [sic], e.g. ``ile vinum''
>
> No, vinum has allready a command history which makes it superior over `ed`.

You can't go back a line with vinum.  Once you've entered it, it gets
processed.

Greg
--
See complete headers for address, home page and phone numbers
finger g...@lemis.com for PGP public key


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: Panic: Invalid longjmp with vinum configured by novice

1999-04-09 Thread Michael Reifenberger
On Fri, 9 Apr 1999, Jacques Vidrine wrote:

> Date: Fri, 09 Apr 1999 12:30:41 -0500
> From: Jacques Vidrine 
> To: Michael Reifenberger 
> Cc: Greg Lehey , FreeBSD-Current 
> Subject: Re: Panic: Invalid longjmp with vinum configured by novice 
> 
> On 9 April 1999 at 11:31, Michael Reifenberger  wrote:
> [snip] 
> > > But vinum(8) doesn't offer
> > > you much in the way of editing facilities either.
> > A command history and commandline editing :-)
> 
> Use ile in ports/misc/lile [sic], e.g. ``ile vinum''
No, vinum has allready a command history which makes it superior over `ed`.

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



Re: Panic: Invalid longjmp with vinum configured by novice

1999-04-09 Thread Jacques Vidrine
On 9 April 1999 at 11:31, Michael Reifenberger  wrote:
[snip] 
> > But vinum(8) doesn't offer
> > you much in the way of editing facilities either.
> A command history and commandline editing :-)

Use ile in ports/misc/lile [sic], e.g. ``ile vinum''

Jacques Vidrine / n...@nectar.com / nec...@freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message



Re: Panic: Invalid longjmp with vinum configured by novice

1999-04-09 Thread Michael Reifenberger
Hi,
On Fri, 9 Apr 1999, Greg Lehey wrote:
...
> > # vinum start
> 
> You don't need to do this unless you already have objects defined from
> an earlier run of vinum.
Ah, ok.
> 
> > # vinum resetconfig
> 
> You never need to do this after a start.  To quote vinum(8):
I was aware of the fact that this command ist not for the normal use.
I just wanted to set a clean startingpoint for this example.

> Not much.  It's trivial to implement, but just another way of shooting
> yourself in the foot.
I find the configfile appropriate for initial confiurations.
But what is the best method if one disk faults and gets replaced.
Then I shouldn't need the overall confguration. 
Unfortunately the documentation is not that specific about this point, one
should need only to recreate the subdisks which laid on the faulty disk after
creating a vinum slice on the fresh disk, right?
Or does vinum replicates itself after the failure onto the fresh disk?
> 
> > I suspect one will not have a r/w filesystem in worst case scenarios
> > for creating vinum createfiles (And even if, `ed` is not my friend.)
> 
> Hmm.  I suppose that might be an argument.  But vinum(8) doesn't offer
> you much in the way of editing facilities either.
A command history and commandline editing :-)

And many thanks for helping anyway!

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



Re: Panic: Invalid longjmp with vinum configured by novice

1999-04-08 Thread Greg Lehey
[Format recovered--see http://www.lemis.com/email/email-format.html]

On Friday,  9 April 1999 at  0:35:07 +0200, Michael Reifenberger wrote:
> Hi,
> I often get to above message while trying to configure vinum.
> Trying the examples from the manpage works, of course.
> Next try.
> What I want to do:
> First creating a non mirrored but striped volume and later add one mirror 
> plex.
>
> I do:
> # vinum start

You don't need to do this unless you already have objects defined from
an earlier run of vinum.

> # vinum resetconfig

You never need to do this after a start.  To quote vinum(8):

 resetconfig

 The resetconfig command completely obliterates the vinum configu-
 ration on a system.  Use this command only when you want to com-
 pletely delete the configuration.  vinum will ask for confirma-
 tion: you must type in the words NO FUTURE exactly as shown:

   # vinum resetconfig

   WARNING!  This command will completely wipe out your vinum
   configuration.  All data will be lost.  If you really want
   to do this, enter the text

   NO FUTURE
   Enter text -> NO FUTURE
   Vinum configuration obliterated

 As the message suggests, this is a last-ditch command.  Don't use
 it unless you have an existing configuration which you never want
 to see again.

Later:

 3.   Some of the commands currently supported by vinum are not really
  needed.  For reasons which I don't understand, however, I find that
  users frequently try the label and resetconfig commands, though es-
  pecially resetconfig outputs all sort of dire warnings.  Don't use
  these commands unless you have a good reason to do so.

> # 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
> vinum create x
> ...
> (Please note the missing 'd' in stripe)
>
> I get:
> ..the panic..
>
> Sigh.

Agreed.  *sigh*.

I found about this problem last night, and I've fixed it, but I have
only just committed it.  It's a result of the change in the kernel
address space.

> BTW: Any chance that the create commands will work interactive from
> within vinum?

Not much.  It's trivial to implement, but just another way of shooting
yourself in the foot.

> I suspect one will not have a r/w filesystem in worst case scenarios
> for creating vinum createfiles (And even if, `ed` is not my friend.)

Hmm.  I suppose that might be an argument.  But vinum(8) doesn't offer
you much in the way of editing facilities either.

Greg
--
When replying to this message, please copy the original recipients.
For more information, see http://www.lemis.com/questions.html
See complete headers for address, home page and phone numbers
finger g...@lemis.com for PGP public key


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message