Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Sep 2002 18:34:22 +0300 (EEST)
From:      Adrian Penisoara <ady@freebsd.ady.ro>
To:        FreeBSD-gnats-submit@FreeBSD.org
Cc:        Greg Lehey <grog@FreeBSD.org>
Subject:   kern/43475: Starting Vinum again while active corrupts the configuration
Message-ID:  <200209291534.g8TFYMn1024778@x.warpnet.ro>

next in thread | raw e-mail | index | archive | help

>Number:         43475
>Category:       kern
>Synopsis:       Starting Vinum again while active corrupts the configuration
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Sep 29 08:40:02 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Adrian Penisoara
>Release:        FreeBSD 4.7-PRERELEASE i386
>Organization:
>Environment:

FreeBSD yoda.warpnet.ro 4.7-PRERELEASE FreeBSD 4.7-PRERELEASE #0: Tue Sep 17 01:
12:06 EEST 2002     ady@yoda.warpnet.ro:/usr/src/sys/compile/YODA  i386

FreeBSD sauron.warpnet.ro 4.6.2-RELEASE FreeBSD 4.6.2-RELEASE #0: Wed Aug 14 21:
23:26 GMT 2002     murray@builder.freebsdmall.com:/usr/src/sys/compile/GENERIC  
i386

  Both systems have Adaptec aic78xx SCSI controllers (ahc(4)) and SCSI disks,
vinum is started and has at least one volume configured and up for the /usr
partition.

  Yoda is SMP (2x P3 450Mhz) and sauron is UP (PPro 200Mhz). If further info
is needed please let me know.

>Description:

  Running "vinum start" while the Vinum kld/daemon is already running and
configured blows up the drives configuration and even produces a panic with
SMP kernels.

>How-To-Repeat:

  While in multiuser and Vinum is already started and configured run
"vinum start" from the command line.

  Or: have Vinum started and configured in multiuser mode then shutdown
the system in single user (with "init 1"), wait for the shell prompt and
exit back to multiuser (with "exit" or "^D").

  Either way you should get a corrupted vinum configuration by now (usually
the drive/disk labels will get corrupted or deleted) or, even worse, your
system will panic (with SMP kernels).


>Fix:

  Workaround: force a "vinum stop" before starting Vinum at bootup.

--- usr/src/etc/rc      Thu May  9 20:39:01 2002
+++ etc/rc      Sat Sep 28 00:51:12 2002
@@ -122,6 +122,7 @@
 
 case ${start_vinum} in
 [Yy][Ee][Ss])
+       vinum stop
        vinum start
        ;;
 esac


  However the offendig bug should be fixed instead of appealing to workarounds.

 Adrian Penisoara
 Ady (@freebsd.ady.ro)

>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209291534.g8TFYMn1024778>