From owner-freebsd-hackers  Sat Mar 23 20:45:55 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA27963
          for hackers-outgoing; Sat, 23 Mar 1996 20:45:55 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id UAA27957
          for <freebsd-hackers@freebsd.org>; Sat, 23 Mar 1996 20:45:49 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA29189; Sun, 24 Mar 1996 15:43:51 +1100
Date: Sun, 24 Mar 1996 15:43:51 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199603240443.PAA29189@godzilla.zeta.org.au>
To: bde@zeta.org.au, dave@kachina.jetcafe.org
Subject: Re: Adding a damn 2nd disk
Cc: andreas@knobel.gun.de, freebsd-hackers@freebsd.org, julian@ref.tfs.com
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>However, the system reads
>>the tables of the disk on the next open of a device on the disk provided
>>no other device on the disk is already open.  

>The raw device? So all I have to do is fdisk this again? 

Any device on the disk.  It depends on whether any other device on the
disk is already open.  Getting the complete list of open disks seems to
require looking at the output of `mount', `pstat -s' and `fstat'.  An
easier way to see if the tables are being refreshed is to set the
kernel's `bootverbose' flag by booting with -v or using a debugger
(e.g., echo 'set bootverbose=1' | gdb -k -w /kernel /dev/mem).  Then
the driver will print annoying messages about the tables when it refreshes
them.  More annoying messages can be printed by setting the kernel's
`dsi_debug' flag using a debugger.

Bruce