From owner-freebsd-current Thu Nov 2 14:26:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (fw2.aub.dk [195.24.1.195]) by hub.freebsd.org (Postfix) with ESMTP id 8755A37B4F9 for ; Thu, 2 Nov 2000 14:26:49 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.9.3) with ESMTP id eA2MQbh01456; Thu, 2 Nov 2000 23:26:37 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Justin T. Gibbs" Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic in vfinddev in -current In-Reply-To: Your message of "Thu, 02 Nov 2000 15:20:38 MST." <200011022220.eA2MKca78033@aslan.scsiguy.com> Date: Thu, 02 Nov 2000 23:26:37 +0100 Message-ID: <1454.973203997@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011022220.eA2MKca78033@aslan.scsiguy.com>, "Justin T. Gibbs" wri tes: >I beleive that I've somehow corrupted my /dev on my laptop. >An ls -l in there causes an instant panic: > >Copied by hand... > >vfinddev(ffffffff,3,c877ac84,10002,1) at vfinddev+0xc > ^^^^^^^^<= NODEV Just fixed in current (I hope) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message