>Number:         21408
>Category:       kern
>Synopsis:       "sd0: no disk label" messages are stupid and annoying
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 30 18:04:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Jason R Thorpe
>Release:        NetBSD 1.6P
>Organization:
Wasabi Systems, Inc.
>Environment:
	
	
System: NetBSD yeah-baby.shagadelic.org 1.6P NetBSD 1.6P (YEAH-BABY-XP) #13: Thu Mar 6 12:04:28 PST 2003 thorpej@yeah-baby.shagadelic.org:/u1/netbsd/src/sys/arch/i386/compile/YEAH-BABY-XP i386
Architecture: i386
Machine: i386
>Description:
	The messages informing whoever is sitting at the console that
	a device has no disklabel are extremely annoying.

	1. It is common for vnd devices to not have disklabels (checking
	   the contents of a makefs(1)'d file system image, for instance).
	   Repeated opening of a vnd device thus fills the message buffer
	   with "vnd0: no disk label" messages.  This is very irritating.

	2. The case where you have an "ataraid" type device where an
	   "ld" instance is buit from "wd" instances; the underlying
	   "wd" devices will not have disk labels, and we get to see
	   this fact annoyingly spewed all over the console (once
	   for each component) when we mount the root file system.

>How-To-Repeat:
	makefs(1) a file system image.  Create and mount a vnd with
	the image.  See the message.  Become greatly annoyed at how
	obnixious the message is.

>Fix:
	Lack of a disk label should not be considered an error.  All
	readdisklabel() routines in machine-dependent code will need
	to be adjusted for this.
>Release-Note:
>Audit-Trail:
>Unformatted: