From owner-freebsd-current  Sat Aug 26 14:09:18 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id OAA01888
          for current-outgoing; Sat, 26 Aug 1995 14:09:18 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id OAA01871
          for <current@freebsd.org>; Sat, 26 Aug 1995 14:08:56 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA17016; Sun, 27 Aug 1995 07:06:11 +1000
Date: Sun, 27 Aug 1995 07:06:11 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199508262106.HAA17016@godzilla.zeta.org.au>
To: current@freebsd.org
Subject: nfs panic after changing cd's
Cc: dfr@render.com
Sender: current-owner@freebsd.org
Precedence: bulk

My nfs client paniced with a null pointer somewhere in nfs_statfs() or
thereabouts.  The server printed:

Aug 26 23:13:48 alphplex /kernel: fhtovp: file start miss 142213208 vs 60
Aug 26 23:13:51 alphplex last message repeated 2 times

This message is from cd9660_vfsops.c (which prints a lot of similar
messages without identifying itself).

My cdrom had been changed.  Usually I mount it at boot time and export
it and never change it and have no problems with cd9660 vs nfs.

I think this bug is known.  It maybe the same as the one reported a day
or two ago where the panic occurred in an lkm'ed file system so that it
wasn't obvious what it was for.

Bruce