vinum related panic in 5.1-BETA2 (long backtrace)

[Lukas Ertl]

On Tue, 27 May 2003, Greg 'groggy' Lehey wrote:

>     * Which version of FreeBSD are you running?

FreeBSD leelou 5.1-BETA FreeBSD 5.1-BETA #1: Thu May 22 16:03:50 CEST 2003
le at leelou:/usr/obj/usr/src/sys/LEELOU  i386

>     * Have you made any changes to the system sources, including
>       Vinum?

No.

>     * Supply the output of the vinum list command. If you can't start
>       Vinum, supply the on-disk configuration, as described below. If
>       you can't start Vinum, then (and only then) send a copy of the
>       configuration file.

2 drives:
D big2                  State: up	/dev/ad2s1d	A: 15286/75804 MB (20%)
D big1                  State: up	/dev/ad0s1d	A: 15286/75804 MB (20%)

8 volumes:
V root                  State: up	Plexes:       2	Size:        150 MB
V home                  State: up	Plexes:       2	Size:       1024 MB
V var                   State: up	Plexes:       2	Size:        500 MB
V usr                   State: up	Plexes:       2	Size:       4096 MB
V usrlocal              State: up	Plexes:       2	Size:       4096 MB
V squid                 State: up	Plexes:       2	Size:       1500 MB
V mp3                   State: up	Plexes:       2	Size:       8192 MB
V dvdrip                State: up	Plexes:       2	Size:         40 GB

16 plexes:
P root.p0             C State: up	Subdisks:     1	Size:        150 MB
P home.p0             C State: up	Subdisks:     1	Size:       1024 MB
P var.p0              C State: up	Subdisks:     1	Size:        500 MB
P usr.p0              C State: up	Subdisks:     1	Size:       4096 MB
P usrlocal.p0         C State: up	Subdisks:     1	Size:       4096 MB
P squid.p0            C State: up	Subdisks:     1	Size:       1500 MB
P mp3.p0              C State: up	Subdisks:     1	Size:       8192 MB
P dvdrip.p0           C State: up	Subdisks:     1	Size:         40 GB
P root.p1             C State: up	Subdisks:     1	Size:        150 MB
P home.p1             C State: up	Subdisks:     1	Size:       1024 MB
P var.p1              C State: up	Subdisks:     1	Size:        500 MB
P usr.p1              C State: up	Subdisks:     1	Size:       4096 MB
P usrlocal.p1         C State: up	Subdisks:     1	Size:       4096 MB
P squid.p1            C State: up	Subdisks:     1	Size:       1500 MB
P mp3.p1              C State: up	Subdisks:     1	Size:       8192 MB
P dvdrip.p1           C State: up	Subdisks:     1	Size:         40 GB

16 subdisks:
S root.p0.s0            State: up	D: big2         Size:        150 MB
S home.p0.s0            State: up	D: big2         Size:       1024 MB
S var.p0.s0             State: up	D: big2         Size:        500 MB
S usr.p0.s0             State: up	D: big2         Size:       4096 MB
S usrlocal.p0.s0        State: up	D: big2         Size:       4096 MB
S squid.p0.s0           State: up	D: big2         Size:       1500 MB
S mp3.p0.s0             State: up	D: big2         Size:       8192 MB
S dvdrip.p0.s0          State: up	D: big2         Size:         40 GB
S root.p1.s0            State: up	D: big1         Size:        150 MB
S home.p1.s0            State: up	D: big1         Size:       1024 MB
S var.p1.s0             State: up	D: big1         Size:        500 MB
S usr.p1.s0             State: up	D: big1         Size:       4096 MB
S usrlocal.p1.s0        State: up	D: big1         Size:       4096 MB
S squid.p1.s0           State: up	D: big1         Size:       1500 MB
S mp3.p1.s0             State: up	D: big1         Size:       8192 MB
S dvdrip.p1.s0          State: up	D: big1         Size:         40 GB

(I don't know if it is relevant, but I'm running an "all-vinum" system
with a mirrored root filesystem.)

>     * Supply an extract of the Vinum history file. Unless you have
>       explicitly renamed it, it will be /var/log/vinum_history. This
>       file can get very big; please limit it to the time around when
>       you have the problems. Each line contains a timestamp at the
>       beginning, so you will have no difficulty in establishing which
>       data is of relevance.

There's no output in vinum_history at the time the panic occurred:

22 May 2003 15:02:19.890586 start home.p1.s0 var.p1.s0 usr.p1.s0
usrlocal.p1.s0 squid.p1.s0 mp3.p1.s0 dvdrip.p1.s0
22 May 2003 17:37:24.521419 l
27 May 2003 08:59:53.658820 *** vinum started ***
27 May 2003 08:59:53.685157 list
27 May 2003 09:00:01.535607 *** vinum started ***
27 May 2003 09:00:01.537087 list

>     * Supply an extract of the file /var/log/messages. Restrict the
>       extract to the same time frame as the history file. Again, each
>       line contains a timestamp at the beginning, so you will have no
>       difficulty in establishing which data is of relevance.

There's nothing relevant in /var/log/messages either.

regards,
le

-- 
Lukas Ertl                             eMail: l.ertl at univie.ac.at
UNIX-Systemadministrator               Tel.:  (+43 1) 4277-14073
Zentraler Informatikdienst (ZID)       Fax.:  (+43 1) 4277-9140
der Universität Wien                   http://mailbox.univie.ac.at/~le/