Re: Device layering work patch #5

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

: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
:...
:disklabel: Warning, old bootblocks detected, install new bootblocks & reinstall the disklabel
:
 
     This is related to work a month or two or three ago, when I expanded
     the number of partitions the disklabel can hold from 8 to 16.

     You have to reinstall the boot blocks for the slice (disklabel -B ...)
     because the old boot blocks were being placed right after partition #8
     instead of partition #16.

: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.

    This is probably new.  I'll fix it today.  I'll probably commit the patch
    today.

: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?

    Yes, it's expected.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>