Date: Mon, 20 Sep 1999 01:16:11 -0700 (PDT) From: norbert.meissner@daimlerchrysler.com To: freebsd-gnats-submit@freebsd.org Subject: i386/13849: dump on vinum r5 freezes system Message-ID: <19990920081611.CC00615A20@hub.freebsd.org>
index | next in thread | raw e-mail
>Number: 13849
>Category: i386
>Synopsis: dump on vinum r5 freezes system
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Sep 20 01:20:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Norbert Meissner
>Release: 3.3
>Organization:
DaimlerChrysler
>Environment:
3.3-RELEASE 'out of the box'
>Description:
A dump on a RAID5 vinum volume causes a freeze of the system. This
happens at dump phase IV (dumping files). After this the system is not
accessible by any key (No console switching, CTRL-ALT-DEL,...), only
pressing RESET-Button or Power cycling helps.
>How-To-Repeat:
build a raid5 vinum volume, for instance my config:
(make diskslices with type vinum)
# disklabel -e da1e (type vinum)
# disklabel -e da2e (type vinum)
# disklabel -e da3e (type vinum)
(write a vinum config file)
drive d1 device /dev/da1e
drive d2 device /dev/da2e
drive d3 device /dev/da3e
volume raid
plex org raid5 256k
sd length 512m drive d1
sd length 512m drive d2
sd length 512m drive d3
(set it up)
# vinum
->create vinum.cfg
->init -vw raid.p0 (this needs some time!)
->quit
# newfs -v /dev/vinum/rraid
# mkdir /mnt/raid
# mount /dev/vinum/raid /mnt/raid
(populate it)
# cp -R /usr/share/doc/usd /mnt/raid
# cd /
# dump -0au -f /dev/nrsa0
Now you hear some hd activity, dump runs through its phases and when
phase IV is reached, the system freezes.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990920081611.CC00615A20>