Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Oct 1999 15:05:09 -0700
From:      Greg Lehey <grog@lemis.com>
To:        dking@malf.net, freebsd-questions@FreeBSD.ORG
Subject:   Re: Panics with Vinum
Message-ID:  <19991020150509.03414@mojave.worldwide.lemis.com>
In-Reply-To: <380B3415.335747B4@stmichael.org>; from D. J. King on Mon, Oct 18, 1999 at 07:52:05AM -0700
References:  <380B3415.335747B4@stmichael.org>

next in thread | previous in thread | raw e-mail | index | archive | help
[Format recovered--see http://www.lemis.com/email/email-format.html]

On Monday, 18 October 1999 at  7:52:05 -0700, D. J. King wrote:
> My configuration is:
>
> AMD K6-3 with 256MB memory
> 2x18GB IBM IDE Disks
>
> FreeBSD 3.3-Release
>
> My Vinum Config is:
>
> drive d1 device /dev/wd2h
> drive d2 device /dev/wd0g
> volume home
>         plex org concat
>                 sd length 12990M drive d1
>         plex org concat
>                 sd length 12990M drive d2
> vinum start
>
> Fatal trap 12
> Fault Virtual Address	0x10
> Fault Code		Supervisor Read, Page Not Present
> Instruction Pointer	0x8:0xc2109317
> Stack Pointer		0x10:0xcf0a8c44
> Frame Pointer		0x10:0xcf0a8c98
> blah, blah, blah
>
> This is repeatable, at least in my environment

It's generally pretty repeatable.  Please read the pages at
http://www.lemis.com/vinum.html for information about Vinum, and
http://www.lemis.com/vinum/bugs.html in particular if you have
problems.  This one is a known bug which is in 3.3-RELEASE (sorry
about that).  It's now fixed.  Get 3.3-STABLE for the fix.  Here's the
text from the web page:

     28 September 1999: If you don't have all device nodes, 'vinum
     start' may panic the machine. Specifically, if you have a disk
     /dev/da0c, you should have the following devices:

     brw-r-----  1 root  operator    4, 0x00010002 Sep 28 12:01 /dev/da0
     brw-r-----  1 root  operator    4,   0 Sep 28 12:01 /dev/da0a
     brw-r-----  1 root  operator    4,   1 Sep 28 12:01 /dev/da0b
     brw-r-----  1 root  operator    4,   2 Sep 28 12:01 /dev/da0c
     brw-r-----  1 root  operator    4,   3 Sep 28 12:01 /dev/da0d
     brw-r-----  1 root  operator    4,   4 Sep 28 12:01 /dev/da0e
     brw-r-----  1 root  operator    4,   5 Sep 28 12:01 /dev/da0f
     brw-r-----  1 root  operator    4,   6 Sep 28 12:01 /dev/da0g
     brw-r-----  1 root  operator    4,   7 Sep 28 12:01 /dev/da0h
     brw-r-----  1 root  operator    4, 0x00020002 Sep 28 12:01 /dev/da0s1
     brw-r-----  1 root  operator    4, 0x00020000 Sep 28 12:01 /dev/da0s1a
     brw-r-----  1 root  operator    4, 0x00020001 Sep 28 12:01 /dev/da0s1b
     brw-r-----  1 root  operator    4, 0x00020002 Sep 28 12:01 /dev/da0s1c
     brw-r-----  1 root  operator    4, 0x00020003 Sep 28 12:01 /dev/da0s1d
     brw-r-----  1 root  operator    4, 0x00020004 Sep 28 12:01 /dev/da0s1e
     brw-r-----  1 root  operator    4, 0x00020005 Sep 28 12:01 /dev/da0s1f
     brw-r-----  1 root  operator    4, 0x00020006 Sep 28 12:01 /dev/da0s1g
     brw-r-----  1 root  operator    4, 0x00020007 Sep 28 12:01 /dev/da0s1h
     brw-r-----  1 root  operator    4, 0x00030002 Sep 28 12:01 /dev/da0s2
     brw-r-----  1 root  operator    4, 0x00040002 Sep 28 12:01 /dev/da0s3
     brw-r-----  1 root  operator    4, 0x00050002 Sep 28 12:01 /dev/da0s4

     In particular, if the /dev/da0s1a devices are missing, we have seen panics. 

     Technical explanation: The function vinum_scandisk was trying to
     read from a drive which had been invalidated. This caused a null
     pointer dereference.

     Status (13 October 1999): Fixed in 4.0-CURRENT (file vinumio.c,
     revision 1.45) and 3.3-STABLE (file vinumio.c, revision
     1.7.2.11).

     Will not be fixed in older releases, if indeed it exists there. 

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


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




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