From adam@veda.is  Tue Mar 25 17:32:04 1997
Received: from veda.is (ubiq.veda.is [193.4.230.60])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA00264
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 25 Mar 1997 17:31:58 -0800 (PST)
Received: (from adam@localhost) by veda.is (8.8.4/8.7.3) id BAA16632; Wed, 26 Mar 1997 01:52:13 GMT
Message-Id: <199703260152.BAA16632@veda.is>
Date: Wed, 26 Mar 1997 01:52:13 GMT
From: Adam David <adam@veda.is>
Reply-To: adam@veda.is
To: FreeBSD-gnats-submit@freebsd.org
Subject: vi large_file --> reboot without panic
X-Send-Pr-Version: 3.2

>Number:         3103
>Category:       kern
>Synopsis:       vi large_file --> reboot without panic
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 25 17:40:01 PST 1997
>Closed-Date:    Wed Apr 15 11:35:47 PDT 1998
>Last-Modified:  Wed Apr 15 11:35:57 PDT 1998
>Originator:     Adam David
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
Veda Internet
>Environment:

	MFS /tmp, NFS /usr /home
	tight diskspace might be a factor
	-current as of 21.Jan.1997 (been like this for months previous)

>Description:

	using vi to edit a huge file results in triggering an instant reboot
	(no panic, no kernel dump) or the machine hangs indefinitely.
	files larger than 2MB seem more likely to do this, but I don't have
	empirical measurements due to reluctance to take the machine out
	of service over and over.

	there's a chance this is already fixed, but I'll not be upgrading to
	Lite-2 until the NFS exec bug is gone, so I don't know for sure yet.

>How-To-Repeat:

	vi /usr/local/news/lib/history  # or some other huge file

>Fix:
	
	as workaround, use a different editor
>Release-Note:
>Audit-Trail:

From: Bill Fenner <fenner@parc.xerox.com>
To: freebsd-gnats-submit@freebsd.org, adam@veda.is
Cc:  Subject: Re: kern/3103: vi large_file --> reboot without panic
Date: Wed, 7 May 1997 21:37:35 PDT

 >there's a chance this is already fixed, but I'll not be upgrading to
 >Lite-2 until the NFS exec bug is gone, so I don't know for sure yet.
 
 Have you gotten a chance to upgrade and try this again yet?
 
 Thanks,
   Bill

From: Bill Fenner <fenner@parc.xerox.com>
To: freebsd-gnats-submit@freebsd.org, adam@veda.is
Cc:  Subject: Re: kern/3103: vi large_file --> reboot without panic
Date: Wed, 7 May 1997 21:37:35 PDT

 >there's a chance this is already fixed, but I'll not be upgrading to
 >Lite-2 until the NFS exec bug is gone, so I don't know for sure yet.
 
 Have you gotten a chance to upgrade and try this again yet?
 
 Thanks,
   Bill

From: Adam David <adam@veda.is>
To: fenner@parc.xerox.com (Bill Fenner)
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/3103: vi large_file --> reboot without panic
Date: Wed, 7 May 1997 22:08:28 +0000 (GMT)

 > >there's a chance this is already fixed, but I'll not be upgrading to
 > >Lite-2 until the NFS exec bug is gone, so I don't know for sure yet.
 > 
 > Have you gotten a chance to upgrade and try this again yet?
 > 
 > Thanks,
 >   Bill
  
 At this very moment I am still hesitant to upgrade to (recent) -current on my
 production machines. Actually, it's more like I am eager to upgrade but cannot
 afford at the moment to be stomped by NFS exec problems. I would prefer local
 caching of NFS executables anyway, but that's several steps away.
 
 Of course you are mainly referring to the problem triggered by vi, which as far
 as I know is still there... but what do I know about it, since I'm not running
 the latest (vm) kernel code.
 
 If someone can convince me and guarantee that the post-lite2 NFS exec panics
 are over, I'll upgrade and get this tested on my environment here (where vi is
 otherwise known to trigger this problem).
 
 --
 Adam David <adam@veda.is>

From: Adam David <adam@veda.is>
To: fenner@parc.xerox.com (Bill Fenner)
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: kern/3103: vi large_file --> reboot without panic
Date: Wed, 7 May 1997 22:08:28 +0000 (GMT)

 > >there's a chance this is already fixed, but I'll not be upgrading to
 > >Lite-2 until the NFS exec bug is gone, so I don't know for sure yet.
 > 
 > Have you gotten a chance to upgrade and try this again yet?
 > 
 > Thanks,
 >   Bill
  
 At this very moment I am still hesitant to upgrade to (recent) -current on my
 production machines. Actually, it's more like I am eager to upgrade but cannot
 afford at the moment to be stomped by NFS exec problems. I would prefer local
 caching of NFS executables anyway, but that's several steps away.
 
 Of course you are mainly referring to the problem triggered by vi, which as far
 as I know is still there... but what do I know about it, since I'm not running
 the latest (vm) kernel code.
 
 If someone can convince me and guarantee that the post-lite2 NFS exec panics
 are over, I'll upgrade and get this tested on my environment here (where vi is
 otherwise known to trigger this problem).
 
 --
 Adam David <adam@veda.is>
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Wed Apr 15 11:35:47 PDT 1998 
State-Changed-Why:  
timed out 
>Unformatted:
