Date: Fri, 17 Sep 2004 18:03:55 GMT From: David Kelly <dkelly@hiwaay.net> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/71824: start_vinum="YES" panics 5.3-BETA4 on boot Message-ID: <200409171803.i8HI3tLa004764@www.freebsd.org> Resent-Message-ID: <200409171810.i8HIAbHD028727@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 71824 >Category: kern >Synopsis: start_vinum="YES" panics 5.3-BETA4 on boot >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 17 18:10:37 GMT 2004 >Closed-Date: >Last-Modified: >Originator: David Kelly >Release: 5.3-BETA4 >Organization: >Environment: FreeBSD Opus.home 5.3-BETA4 FreeBSD 5.3-BETA4 #0: Thu Sep 16 19:53:35 CDT 2004 dkelly@Opus.home:/usr/obj/usr/src/sys/GENERIC i386 >Description: Attempts to autostart vinum at boot cause kernel panic after 1 second of uptime. Last things displayed before freezing are: vinum: loaded panic: unmount: dangling vnode cpuid = 0 uptime: 1s Vinum volume was created with "vinum stripe -v /dev/ad4s1d /dev/ad6s1d" originally in 5.2.1. Can't make it not reproduce this problem in 5.3-BETA. Previously worked in 5.2.1-p9 but not totally without issues. In p9 vinum often did not remember at boot that the vinum drives were to be striped but did remember. Had to boot single user and repeat the above command to restore that information and create /dev/vinum/vinum0. Due to this problem I'm currently running a totally stock GENERIC. # vinum printconfig # Vinum configuration of Opus.home, saved at Fri Sep 17 12:59:44 2004 drive vinumdrive1 device /dev/ad6s1d drive vinumdrive0 device /dev/ad4s1d volume vinum0 plex name vinum0.p0 org striped 558s vol vinum0 sd name vinum0.p0.s0 drive vinumdrive0 plex vinum0.p0 len 319571622s driveoffset 265s plexoffset 0s sd name vinum0.p0.s1 drive vinumdrive1 plex vinum0.p0 len 319571622s driveoffset 265s plexoffset 558s >How-To-Repeat: Machine is a Dell Power Edge 400SC, P4-2.8G-512k, HT disabled. MB is Intel 875 based. The problem vinum drives are on SATA interfaces. System boot drive is PATA. The s1b partition on each drive is used as swap. I always have this problem if vinum is started from /etc/rc.conf. Doesn't matter if vinum is loaded in /boot/loader.conf or not. >Fix: Boot single user. Manually mount filesystems. Manually run "vinum start" and then mount that one too. Sometimes (less often than in 5.2.1) vinum forgets its configuration and the "vinum stripe" command above has to be reapplied. A bit cleaner solution has been to comment out the vinum start in /etc/rc.conf and remove the fs entry from /etc/fstab. System boots cleanly to multiuser. Then "vinum start" works, and "mount /dev/vinum/vinum0 /usr5" finishes the task. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409171803.i8HI3tLa004764>