Date: Fri, 6 Jun 2003 15:16:26 +0930 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/52916: vinum causes panic after start/stop/... cycle, easy to reproduce Message-ID: <20030606054626.GD72838@wantadilla.lemis.com> In-Reply-To: <200306060530.h565UEFs038804@freefall.freebsd.org> References: <200306060530.h565UEFs038804@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Thursday, 5 June 2003 at 22:30:14 -0700, Greg 'groggy' Lehey wrote:
>
> I'm guessing this has something to do with md devices. Do you use
> any? I don't, and every 'vinum start' created one. I've committed a
> fix to vinum(8) (revision 1.31.2.6 of src/sbin/vinum/commands.c).
> Please try it and tell me if it fixes the problem. Here it is again
> to save you cvsupping:
>
> diff -w -u -r1.31.2.5 commands.c
> --- commands.c 4 May 2002 05:04:14 -0000 1.31.2.5
> +++ commands.c 6 Jun 2003 05:08:43 -0000
> @@ -275,6 +275,10 @@
> char reply[32];
> int error;
> =20
> + if (! isatty (STDIN_FILENO)) {
> + fprintf (stderr, "Please enter this command from a tty device\n");
> + return;
> + }
> printf(" WARNING! This command will completely wipe out your vinum co=
> nfiguration.\n"
> " All data will be lost. If you really want to do this, enter the =
> text\n\n"
> " NO FUTURE\n"
Ugh. Did GNATS do that?
Anyway, don't bother. I can now reproduce the problem more easily :-(
Greg
--
See complete headers for address and phone numbers
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)
iD8DBQE+4CqyIubykFB6QiMRAr2AAJ0VT/xDZlVcSQfWKpQSz/OuMfa83wCdGPD2
tGKAWhgGR+rPELzsEZ9VR4M=
=Y//I
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030606054626.GD72838>