From nobody@FreeBSD.ORG Mon Sep 20 01:16:11 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id CC00615A20; Mon, 20 Sep 1999 01:16:11 -0700 (PDT)
Message-Id: <19990920081611.CC00615A20@hub.freebsd.org>
Date: Mon, 20 Sep 1999 01:16:11 -0700 (PDT)
From: norbert.meissner@daimlerchrysler.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: dump on vinum r5 freezes system
X-Send-Pr-Version: www-1.0

>Number:         13849
>Category:       i386
>Synopsis:       dump on vinum r5 freezes system
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    grog
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Sep 20 01:20:01 PDT 1999
>Closed-Date:    Mon Nov 27 23:04:10 PST 2000
>Last-Modified:  Mon Nov 27 23:04:44 PST 2000
>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:
Responsible-Changed-From-To: freebsd-bugs->grog  
Responsible-Changed-By: cpiazza 
Responsible-Changed-When: Mon Sep 20 15:56:45 PDT 1999 
Responsible-Changed-Why:  
Vinum is grog's baby 
State-Changed-From-To: open->feedback 
State-Changed-By: grog 
State-Changed-When: Mon Sep 20 18:06:50 PDT 1999 
State-Changed-Why:  
Waiting for feedback from submitter. 
State-Changed-From-To: feedback->closed 
State-Changed-By: grog 
State-Changed-When: Mon Nov 27 23:04:10 PST 2000 
State-Changed-Why:  
No feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=13849 
>Unformatted:

Greg Lehey, 21 September 1999

From the man page vinum(8):

   Reporting problems with Vinum

     If you find any bugs in vinum, please report them to Greg Lehey
     <grog@lemis.com>.  Supply the following information:

     o   The output of the vinum list command.

     o   Any messages printed in /var/log/messages. All such messages will be
         identified by the text vinum at the beginning.

     o   If you have a panic, a stack trace as described above.

     4.   The RAID-5 functionality is new in FreeBSD 3.3.  Some problems have
          been reported with vinum in combination with soft updates, but these
          are not reproducible on all systems.  If you are planning to use
          vinum in a production environment, please test carefully.

Are you using soft updates?

Since reading this PR, I discover that the information you supplied is
only part of the story.  From a mail message you sent to
FreeBSD-questions I learn:

   2. I was not able to make a dump from a vinum volume (raid5, mirror
      and stripe tested).  In the worst case (raid5) the whole system
      freezes! Only the reset button shows effect. In the other cases
      dump aborts with the message "bad magic number in sblock".

You *must* state everything you know in a PR; otherwise you'll be
causing people to do unnecessary work.

Please build a kernel with the line

       options DDB

When the system hangs, press ctrl-alt-esc.  You should get a ddb
prompt.  Enter the comand 'panic' and press Enter twice.  Read
vinum(4) for instructions about how to analyse the dump.  If you can
arrange for access to your machine, I can also take a look.  At the
very least I need a stack trace.

Greg Lehey, 28 November 2000

This PR has been in feedback state for over a year.  I can only assume
that the submitter is no longer interested, probably because the
problem has gone away.  PR closed.
