NetBSD Problem Report #3153
Received: (qmail-queue invoked from smtpd); 28 Jan 1997 15:56:00 -0000
Message-Id: <199701281549.QAA01785@snert.pilhuhn.de>
Date: Tue, 28 Jan 1997 16:49:13 +0100 (MET)
From: hwr@pilhuhn.de
Reply-To: hwr@pilhuhn.de
To: gnats-bugs@gnats.netbsd.org
Subject: vmstat/iostat exits when no disk on system
X-Send-Pr-Version: 3.95
>Number: 3153
>Category: port-i386
>Synopsis: vmstat/iostat exits when no disk on system
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: gnats-admin
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Jan 28 08:05:00 +0000 1997
>Closed-Date: Tue Mar 04 23:35:12 +0000 1997
>Last-Modified: Wed Mar 05 07:36:21 +0000 1997
>Originator: Heiko W.Rupp
>Release: 1.1
>Organization:
private
>Environment:
System: NetBSD snert.pilhuhn.de 1.1 NetBSD 1.1 (SNERT+PPP) #0: Mon Jan 20 15:15:19 MET 1997 hwr@snert.pilhuhn.de:/usr/src/sys/arch/i386/compile/SNERT+PPP i386
>Description:
When calling vmstat on system that has no hard drive (e.g. a NFS system):
quaak!1> vmstat
vmstat: dk_ndrive -1
The same also applies to iostat:
quaak# iostat
iostat: invalid dk_ndrive -1
systat(8) also has some problems
>How-To-Repeat:
Build a system that boots from a floppy and that gets root and swap via NFS.
Then start vmstat.
>Fix:
in vmstat.c:
if (dk_ndrive <= 0) {
(void)fprintf(stderr, "vmstat: dk_ndrive %d\n", dk_ndrive);
exit(1);
remove the exit and just remember that no disks are present.
>Release-Note:
>Audit-Trail:
From: hwr@pilhuhn.de (Heiko W.Rupp)
To: gnats-bugs@gnats.netbsd.org, gnats-admin@NetBSD.ORG
Cc: bugs@NetBSD.ORG
Subject: Re: port-i386/3153: vmstat/iostat exits when no disk on system
Date: Tue, 28 Jan 1997 18:42:16 +0100
gnats-bugs@gnats.netbsd.org writes:
> Thank you very much for your problem report.
> It has the internal identification `port-i386/3153'.
> The individual assigned to look at your
> bug is: gnats-admin (GNATS administrator).
>
> >Category: port-i386
> >Responsible: gnats-admin (GNATS administrator)
> >Synopsis: vmstat/iostat exits when no disk on system
> >Arrival-Date: Tue Jan 28 08:05:00 1997
Please close this one as I made the mistake of booting a different
kernel than the one that the kernel data was read from .. perhaps
there could be some 'consistency check' when running kvm_mkdb in order
to find out if the image on disk has the same symbol location than the
booted kernel. If not, then spit out a warning message. I guess that
has been discussed several times in the past though.
Sorry for any inconvenience
--
Heiko W.Rupp Gerwigstr.5 D-76131 Karlsruhe +49 721 9661524
In a Rome laundry: Ladies, leave your clothes here and spend the
afternoon having a good time.
State-Changed-From-To: open->closed
State-Changed-By: mikel
State-Changed-When: Tue Mar 4 23:35:12 1997
State-Changed-Why:
if this was ever a problem, it has been fixed in -current. closed by
submitter request.
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.