Re: Device layering work patch #5

[YONETANI Tomokazu <qhwt+dragonfly-kernel@xxxxxxxxxx>]

Hi.
On Mon, May 17, 2004 at 07:55:25PM -0700, Matthew Dillon wrote:
>     Here's device patch #5:
> 
> 	fetch http://apollo.backplane.com/DFlyMisc/dev05.patch
> 
>     This patch is the same as #4 but fixes two additional bugs:  A
>     disklabel -e crash, and removes warnings about devices already being open.

Compiled and installed kernel/world on an IBM Netfinity 6000R, and the
new kernel survived make -s -j16 buildworld. As this machine is using
a partion on ServerRAID as root filesystem, I haven't tested unloading
of ips.ko after it booted.

I noticed that `disklabel -r ipsd0s1' showed a warning message
at the end:

8 partitions:
#        size   offset    fstype   [fsize bsize bps/cpg]
  a:  1048576        0    4.2BSD     2048 16384    89   # (Cyl.    0 - 65*)
  b:  1048576  1048576      swap                        # (Cyl.   65*- 131*)
  c: 88859043        0    unused        0     0         # (Cyl.    0 - 5552*)
  d:  2097152  2097152    4.2BSD     2048 16384    89   # (Cyl.  131*- 262*)
  e:  8388608  4194304    4.2BSD     2048 16384    89   # (Cyl.  262*- 786*)
  f: 76276131 12582912    4.2BSD     2048 16384    89   # (Cyl.  786*- 5552*)
disklabel: Warning, old bootblocks detected, install new bootblocks & reinstall the disklabel

And vn(4) stopped working:
# vnconfig -e -s labels,reserve -S 64m vn0
vnconfig: /dev/vn0: Device not configured

I'm going to revert to older kernel to see if these are new.


BTW, I'm seeing a lot of messages as follows:

May 19 22:14:22 fred /kernel: Z1reference dev 0xc0389778 urandom(minor=00000004) refs=2
May 19 22:14:22 fred /kernel: Y2release   dev 0xc0389778 urandom(minor=00000004) refs=1

I know they are debug messages, but ones containing 'urandom' is filling
up the log. Is this expected?