From owner-freebsd-current  Fri May 10 06:44:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA16473
          for current-outgoing; Fri, 10 May 1996 06:44:44 -0700 (PDT)
Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA16466
          for <freebsd-current@freefall.freebsd.org>; Fri, 10 May 1996 06:44:40 -0700 (PDT)
Received: from zyzzyva.com (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.7.5/8.6.11) with ESMTP id IAA22529; Fri, 10 May 1996 08:41:02 -0500 (CDT)
Message-Id: <199605101341.IAA22529@sierra.zyzzyva.com>
To: "Christoph P. Kukulies" <kuku@gilberto.physik.rwth-aachen.de>
cc: freebsd-current@freefall.freebsd.org
Subject: Re: -current kernel panics 
In-reply-to: kuku's message of Fri, 10 May 1996 09:30:03 +0200.
         <199605100730.JAA13456@gilberto.physik.rwth-aachen.de> 
X-uri: http://www.zyzzyva.com/
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 10 May 1996 08:41:02 -0500
From: Randy Terbush <randy@zyzzyva.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> I didn't notice that my / FS was at 103% due to some kernels and
> other stuff that had cumulated in / and /root.
> 
> After bringing that back to normal conditions the same kernel (newly
> built though) didn't panic.
> 
> I was doing a mv kernel /kernel ; sync ; reboot frequently at that time
> and may be there is some strangeness when the root file system is full
> such that not all pages are flushed or something leaving an unusable kernel
> in / though I think it shouldn't behave that strange or at least resort
> with an error message. I will still try to reproduce it.
> 
> 
> --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de

I had the same problem recently when a /var partition filled on
a -stable system.